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: Tue, 21 Mar 2017 13:37:04 -0400 From: "J. Bruce Fields" <bfields@...ldses.org> To: Jeff Layton <jlayton@...hat.com> Cc: Christoph Hellwig <hch@...radead.org>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, linux-nfs@...r.kernel.org, linux-ext4@...r.kernel.org, linux-btrfs@...r.kernel.org, linux-xfs@...r.kernel.org Subject: Re: [RFC PATCH v1 00/30] fs: inode->i_version rework and optimization On Tue, Mar 21, 2017 at 01:23:24PM -0400, Jeff Layton wrote: > On Tue, 2017-03-21 at 12:30 -0400, J. Bruce Fields wrote: > > - NFS doesn't actually require that it increases, but I think it > > should. I assume 64 bits means we don't need a discussion of > > wraparound. > > I thought NFS spec required that you be able to recognize old change > attributes so that they can be discarded. I could be wrong here though. > I'd have to go back and look through the spec to be sure. https://tools.ietf.org/html/rfc7862#section-10 --b.
Powered by blists - more mailing lists