| 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
| ||
|
Date: Wed, 13 Feb 2013 10:14:55 -0500 From: Theodore Ts'o <tytso@....edu> To: "J. Bruce Fields" <bfields@...ldses.org> Cc: linux-ext4@...r.kernel.org, sandeen@...hat.com, Bernd Schubert <bernd.schubert@...m.fraunhofer.de>, gluster-devel@...gnu.org Subject: Re: regressions due to 64-bit ext4 directory cookies On Wed, Feb 13, 2013 at 08:31:31AM -0500, J. Bruce Fields wrote: > They're assuming they can take the high bits of the cookie for their own > use. > > (In more detail: they're spreading a single directory across multiple > nodes, and encoding a node ID into the cookie they return, so they can > tell which node the cookie came from when they get it back.) > > That works if you assume the cookie is an "offset" bounded above by some > measure of the directory size, hence unlikely to ever use the high > bits.... Right, but why wouldn't a nfs export option solave the problem for gluster? Basically, it would be nice if we did not have to degrade locally running userspace applications by globally turning off 64-bit telldir cookies just because there are some broken cluster file systems and nfsv3 clients out there. And if we are only turning off 64-bit cookies for NFS, wouldn't it make sense to make this be a NFS export option, as opposed to a mount option? Regards, - Ted -- 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
Powered by blists - more mailing lists