Messages in this thread | | | Subject | Re: Possible permissions bug on NFSv3 kernel client | From | Trond Myklebust <> | Date | Fri, 30 Apr 2004 16:39:57 -0400 |
| |
On Fri, 2004-04-30 at 16:17, Pascal Schmidt wrote: > Then it's at least inconsistent with local filesystem behaviour. fsck > has no problem opening device nodes for writing on my root filesystem > even though it is mounted read-only at that point.
So why do you think that is inconsistent with my statement: "the permissions checking has to be done by the server, period"?
The read-only mount option is a *local* override of the write permissions on the server. It applies to regular files, directories, and soft links *only*. The read-only mount option does *not apply* to char/block devices such as /dev/hd[a-z]*, /dev/tty*. Permission checks on open() for those devices are done on the server *only* via the ACCESS rpc call.
This should be entirely consistent with local file behaviour. Particularly since the code to deal with the read-only mount option in nfs_permission() was pretty much cut-n-pasted from vfs_permission().
Cheers, Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |