linux-kernel - Re: [RFC] Union mount readdir support in glibc

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, 14 Mar 2008 05:39:25 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Ulrich Drepper <drepper@...hat.com>
Cc:	bharata@...ux.vnet.ibm.com, libc-alpha@...rceware.org,
	Jan Blunck <jblunck@...e.de>, Erez Zadok <ezk@...sunysb.edu>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	Christoph Hellwig <hch@....de>, Mingming Cao <cmm@...ibm.com>,
	Dave Hansen <haveblue@...ibm.com>
Subject: Re: [RFC] Union mount readdir support in glibc

On Thu, Mar 13, 2008 at 08:53:48PM -0700, Ulrich Drepper wrote:

> To handle union FS at userlevel somewhere in that code sequence (perhaps
> in the fstat call) we'd have to recognize such mounts.

*Snort*

How about "the first entry returned by getdents(3) after open() is a whiteout
for e.g. '.'"?  No fstat needed, zero impact for normal directories,
zero impact for any binaries on old kernels (where you wouldn't have
unions) and zero impact for old binaries on new kernels unless they
do getdents() on directory that happens to be a union.

And no lockstep...

>  Before any
> agreement on userlevel sorting can be made you'll have to answer a
> question Roland already asked:
> 
> - - How does this work with NFS?

It won't, kernel-side or done in userland.

> re seeking: you have to support seeking.  There is no way around it.

Actually, do we really need it other than to 0 and to current position
(i.e. full rewind and a no-op)?
--
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/