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:	Wed, 12 Mar 2008 09:58:58 +0530
From:	Bharata B Rao <bharata@...ux.vnet.ibm.com>
To:	Roland McGrath <roland@...hat.com>
Cc:	libc-alpha@...rceware.org, Jan Blunck <jblunck@...e.de>,
	Erez Zadok <ezk@...sunysb.edu>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, viro@...iv.linux.org.uk,
	Christoph Hellwig <hch@....de>,
	Ulrich Drepper <drepper@...hat.com>,
	Mingming Cao <cmm@...ibm.com>,
	Dave Hansen <haveblue@...ibm.com>
Subject: Re: [RFC] Union mount readdir support in glibc

On Tue, Mar 11, 2008 at 01:09:29AM -0700, Roland McGrath wrote:
> 
> This really is the kernel filesystem's problem.  It just doesn't make sense
> to expect userland to implement half of your directory semantics for you.

I agree that we are asking glibc to handle part of the union mount
semantics in readdir. But we have tried handling directory listing of
union entirely inside the kernel, but the results haven't been so good.
(http://lkml.org/lkml/2007/12/5/147). Recently Al Viro suggested that we
do this in the userland and he felt that is the only sane way of doing this.
Infact I had mentioned about this approach to Ulrich briefly during
FOSS.IN and he sounded positive to the idea of maintaining a dirent
cache for duplicate elimination as long as it doesn't slowdown normal
users.

Regards,
Bharata.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ