linux-kernel - Re: If not readdir() then what?

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: <461E6DF5.6040808@zytor.com>
Date:	Thu, 12 Apr 2007 10:35:49 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"J. Bruce Fields" <bfields@...ldses.org>
CC:	Theodore Tso <tytso@....edu>, Neil Brown <neilb@...e.de>,
	Jörn Engel <joern@...ybastard.org>,
	Christoph Hellwig <hch@...radead.org>,
	Ulrich Drepper <drepper@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: If not readdir() then what?

J. Bruce Fields wrote:
> On Thu, Apr 12, 2007 at 08:21:16AM -0400, Theodore Tso wrote:
>> Again, compared to a directory fd cache, what you're proposing a huge
>> hit to the filesystem, and at the moment, given that telldir/seekdir
>> is rarely used by everyone else, it's mainly NFS which is the main bad
>> actor here by insisting on the use of a small 31/63-bit cookie as a
>> condition of protocol correctness.
> 
> If we want to get bigger cookies into the protocol, then the sooner we
> start working on that the better....  How big is big enough?  And is a
> larger cookie sufficient on its own?
> 

Any fixed size is too small.  It should be a dynamic size.

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