| 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
| ||
|
Message-Id: <1180578314.6696.24.camel@heimdal.trondhjem.org> Date: Wed, 30 May 2007 22:25:14 -0400 From: Trond Myklebust <trond.myklebust@....uio.no> To: cmm@...ibm.com Cc: Andreas Dilger <adilger@...sterfs.com>, jean-noel.cordenner@...l.net, linux-ext4@...r.kernel.org, nfsv4@...ux-nfs.org, linux-fsdevel@...r.kernel.org Subject: Re: [patch 2/2] i_version update - ext4 part On Wed, 2007-05-30 at 16:48 -0700, Mingming Cao wrote: > On Tue, 2007-05-29 at 16:58 -0600, Andreas Dilger wrote: > > I don't know what the NFS requirements for the version are. There may > > also be some complaints from others if the i_version is 64 bits because > > this contributes to generic inode growth and isn't used for other > > filesystems. > > > That should benefit for other filesystems, as I thought this NFS > requirements apply to all filesystems. Right. The point here is that the NFS protocol needs to impose certain requirements on _all_ filesystems that want to be supported, and so it is in the interest of everyone to have a generic update mechanism available in the VFS in order to avoid code (and bug) replication. Now if Lustre doesn't care about NFS compatibility, then I suppose it would be fairly easy to engineer the i_version update interface to allow them to use that field in whatever way suits them best. Trond - 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