| 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, 12 Apr 2011 07:56:11 -0400 From: Trond Myklebust <Trond.Myklebust@...app.com> To: "J. R. Okajima" <hooanon05@...oo.co.jp> Cc: linux-kernel@...r.kernel.org Subject: Re: O_EXCL in NFSv3 On Tue, 2011-04-12 at 16:35 +0900, J. R. Okajima wrote: > Hello Trond, > > The commit in v2.6.37 > c0204fd 2010-09-17 NFS: Clean up nfs4_proc_create() > looks totally dropping O_EXCL flag from NFSv3. > But fs/nfs/nfs3proc.c:nfs3_proc_create() and > fs/nfsd/nfs3proc.c:nfsd3_proc_create() still expect O_EXCL to be passed. > > And the commit log says "Clean up nfs4_proc_create()". > Is this change for NFSv3 intentional? > Actually O_EXCL in NFSv3 doesn't work in v2.6.37 and later. Doesn't commit 8a0eebf66e3b1deae036553ba641a9c2bdbae678 (NFS: Fix NFSv3 exclusive open semantics) fix this? It should be in the stable tree. -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@...app.com www.netapp.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