linux-kernel - Re: Btrfs trees for linux-next

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]

Date:	Tue, 16 Dec 2008 02:39:57 +0100
From:	"Kay Sievers" <kay.sievers@...y.org>
To:	"Chris Mason" <chris.mason@...cle.com>
Cc:	"Andreas Dilger" <adilger@....com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Stephen Rothwell" <sfr@...b.auug.org.au>,
	linux-kernel@...r.kernel.org, linux-btrfs@...r.kernel.org,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: Btrfs trees for linux-next

On Tue, Dec 16, 2008 at 02:37, Chris Mason <chris.mason@...cle.com> wrote:
> On Mon, 2008-12-15 at 23:55 +0100, Kay Sievers wrote:
>> On Mon, Dec 15, 2008 at 22:03, Andreas Dilger <adilger@....com> wrote:
>> > On Dec 11, 2008  09:43 -0500, Chris Mason wrote:
>> >> The multi-device code uses a very simple brute force scan from userland
>> >> to populate the list of devices that belong to a given FS.  Kay Sievers
>> >> has some ideas on hotplug magic to make this less dumb.  (The scan isn't
>> >> required for single device filesystems).
>> >
>> > This should use libblkid to do the scanning of the devices, and it can
>> > cache the results for efficiency.  Best would be to have the same LABEL+UUID
>> > for all devices in the same filesystem, and then once any of these devices
>> > are found the mount.btrfs code can query the rest of the devices to find
>> > the remaining parts of the filesystem.
>>
>> Which is another way to do something you should not do that way in the
>> first place, just with a library instead of your own code.
>>
>
> Well, its the same library everyone else is using to do things they
> shouldn't be doing ;)

Util-linux-ng can be configured to use libvolume_id and udev data, and
it's not used in SUSE and Ubuntu for exactly the reason mentioned. :)

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/