| 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, 5 Jun 2007 13:56:48 -0400 From: Jeff Layton <jlayton@...hat.com> To: nfsv4@...ux-nfs.org, nfs@...ts.sourceforge.net Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org Subject: [PATCH 0/2] intro: make NFSv4 exclusive open calls set and use the bitmask in the reply Around a year ago, Chris Lalancette posted a patch to make it so that when an EXCLUSIVE nfs4 create is done, that the mtime and atime get properly updated in the following setattr call. At the time Trond replied that that approach was incorrect and that we need to check the bitmask in the reply to know what attributes need to be updated. The original thread is here: http://linux-nfs.org/pipermail/nfsv4/2006-June/004489.html The following patchset is a first stab at making the Linux client and server adhere to the correct NFS4 exclusive open semantics. As always, comments are appreciated... -- Jeff Layton <jlayton@...hat.com> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists