linux-ext4 - Re: [PATCH 0/3] Move fsck from e2fsprogs to util-linux-ng

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080207134105.GU27119@mit.edu>
Date:	Thu, 7 Feb 2008 08:41:05 -0500
From:	Theodore Tso <tytso@....EDU>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	Karel Zak <kzak@...hat.com>, Matthias Koenig <mkoenig@...e.de>,
	util-linux-ng@...r.kernel.org, linux-ext4@...r.kernel.org
Subject: Re: [PATCH 0/3] Move fsck from e2fsprogs to util-linux-ng

On Thu, Feb 07, 2008 at 01:37:43AM +0100, Kay Sievers wrote:
> 
> Care to explain what ext4 development has to do with the generic
> fsck program?  I don''t see any convincing reason not to move that
> now.

Fsck and mount (and especially mount) needs to be linked against the
very latest blkid library in order to make sure things work, and when
we spread out packages across the various different packages, it means
updating things to assure correct functionality is that much harder.

It also means getting the right ext4 detection routines into vol_id,
and in the past I've had real problems getting patches that fix real
bugs in vol_id past you, and I'm just too busy right now to deal with
that right now.

						- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html