linux-ext4 - Re: [PATCH, RFC] mke2fs: get device topology values from blkid

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:	Fri, 18 Sep 2009 08:20:24 -0600
From:	Andreas Dilger <adilger@....com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH, RFC] mke2fs: get device topology values from blkid

On Sep 18, 2009  09:04 -0500, Eric Sandeen wrote:
> Andreas Dilger wrote:
>>> +	rc = blkid_probe_set_device(pr, fd, 0, 0);
>>
>> Is this in the e2fsprogs blkid code yet?  I'm guessing not, since you
>
> right, not yet.  I don't know what the long-term plan is for e2fsprogs  
> blkid; keeping 2 trees in sync seems like a lot of work w/o much gain...

I thought that was Ted's plan?  We usually recommend people to update to
the latest e2fsprogs, yet not everyone will be able to upgrade to the
latest util-linux, especially if it is pulling in other libraries that
can cause package conflicts (e.g. with xfstools or similar).

>> Either this needs to be configured in, or you need to upgrade the
>> blkid included with e2fsprogs to handle this.
>
> Yep, that's why I said "It'll also need some config-fu to be sure we've  
> got a blkid which has these calls...." :) and why I was asking about  
> moving the in-tree headers slightly out of the way.

Sigh, it helps if I read the whole email, I guess... :-)

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

--
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