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, 11 Jul 2007 12:57:24 -0400 From: "J. Bruce Fields" <bfields@...ldses.org> To: Mingming Cao <cmm@...ibm.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org, nfsv4@...ux-nfs.org, linux-kernel@...r.kernel.org Subject: Re: [EXT4 set 4][PATCH 1/5] i_version:64 bit inode version On Tue, Jul 10, 2007 at 08:19:16PM -0400, Mingming Cao wrote: > On Tue, 2007-07-10 at 18:22 -0700, Andrew Morton wrote: > > And how does the NFS server know that the filesystem implements i_version? > > Will a zero-value of i_version have special significance, telling the > > server to not send this attribute, perhaps? > > Bruce raised up this question a few days back when he reviewed this > patch, I think the solution is add a superblock flag for fs support > inode versioning, probably at VFS layer? Sounds fine. As long as it's something that's standard across filesystems, then I can just do something like if (sb->s_flags & MS_CHANGEATTR) /* return i_version to client as change attribute */ else /* return ctime to client as change attribute */ --b. - 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