>1. (posted on Oct 16, which is merged as -DNFS_SECURITY_HOLE feature)
>To address the problem of opening a file for write.
>The higher branch is writable(any filesystem), the lower is nfs which is
>exported as readonly. The parent dir of the file does not exist on the
>writable branch, but exists on the nfs branch. And its permission bits
>are set as writable(0755 or somethihg).
>After applying the patch, unionfs ignores the response from the nfs
>server EACCES and believes the result of test of the dir's
>mode(permission bits).

Strange thing here:

12:40 shanghai:/home/jengelh # mount lo:/home/Video /mnt -t nfs 
12:40 shanghai:/home/jengelh # cd /mnt/
12:40 shanghai:/mnt # touch it
touch: cannot touch `it': Read-only file system

You said it returns EACCES?
I am using 2.6.13.0.


Jan Engelhardt
-- 
| Alphagate Systems, http://alphagate.hopto.org/
| jengelh's site, http://jengelh.hopto.org/
_______________________________________________
unionfs mailing list
[email protected]
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs

Reply via email to