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: Fri, 21 Mar 2014 10:39:27 -0400 From: tytso@....edu To: Ben Hutchings <ben@...adent.org.uk> Cc: 738758@...s.debian.org, Christoph Hellwig <hch@...radead.org>, Andreas Dilger <adilger@...ger.ca>, Ext4 Developers List <linux-ext4@...r.kernel.org>, "1o5g4r8o@...il.com" <1o5g4r8o@...il.com> Subject: Re: Bug#738758: [PATCH] ext4: kill i_version support for Hurd-castrated file systems On Thu, Mar 20, 2014 at 05:30:32PM +0000, Ben Hutchings wrote: > > It looks like ext2 and ext3 would always initialise i_version to 1 in > memory; does it matter that you're changing that to 0 for Hurd > filesystems? No, NFS only cares that the i_version number has changed, and it's mainly important if you have two clients trying to simultaneously access the same file, so they get a signal that they need to invalidate their locally cached metadata (or data, in the case of NFSv4). But Hurd only supports NFSv2, and the performance is such that I doubt anyone would be all that interested in using a Hurd server as a NFS server for even a small workgroup, let alone a department, so this is unlikely to be a big deal. Cheers, - 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