On Mon, 2014-06-09 at 10:46 -0400, J. Bruce Fields wrote: > On Sat, Jun 07, 2014 at 07:48:21PM -0700, Philippe Troin wrote: > > Hi Trond & Christoph, > > > > It's still broken, but in a different way. > > The phantom attrs are gone, but the attr/acl interaction is still > > uncertain. > > > > I have tested vanilla 3.14.5 + this patch on x86_64. > > Mount options are the same as last time (NFSv3). > > > > This is what I see on the client: > > > > nfsv3client% mkdir x > > nfsv3client% cd x > > nfsv3client% getfattr -m '.*' . > > nfsv3client% getfacl . > > # file: . > > # owner: phil > > # group: phil > > user::rwx > > group::rwx > > other::r-x > > > > OK so far: no more phantom attrs. > > This is where things get dodgy: > > > > nfsv3client% setfacl -m u:root:r . > > nfsv3client% getfacl . > > # file: . > > # owner: phil > > # group: phil > > user::rwx > > user:root:r-- > > group::rwx > > mask::rwx > > other::r-x > > > > nfsv3client% getfattr -m '.*' . > > [1] 2123 segmentation fault getfattr -m '.*' . > > Is there a backtrace or anything in the system logs? No, nothing but the SIGSEGV getting logged in dmesg. Since I've tested on 3.14.5, 3.14.6 came out, and contains NFSd related patches that look to address further ACL issues. I'm going to be trying that out. Phil. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
