Re: open(..., O_CREAT|O_EXCL, 0400) on aufs over nfs4

Hello Pip, I am still considering how to support atomic_open(), but all of my approach are not good. And I am start thinking that your approach is better eventually. Here is what I thought. If you have any comment, please let me know. Support for a branch who has its -atomic_open()

Re: open(..., O_CREAT|O_EXCL, 0400) on aufs over nfs4

Pip Cet: I've taken the code from fuse/dir.c and modified it slightly to provide a pretty minimal workaround, by creating the file with read/write permission first and then revoking that permission in a separate call to aufs_setattr if necessary. That's not perfect behavior (there is a window

open(..., O_CREAT|O_EXCL, 0400) on aufs over nfs4

I'm running into a problem using tar(1) to create a read-only file on an aufs file system with two nfs4 branches. test@sivtar-8e3b7f91b4ed:~/test$ ls test@sivtar-8e3b7f91b4ed:~/test$ echo test x test@sivtar-8e3b7f91b4ed:~/test$ chmod 0400 x