On Fri Dec 31 2010 at 19:45:26 +0000, David Laight wrote: > On Fri, Dec 31, 2010 at 06:16:41PM +0000, Antti Kantee wrote: > > Module Name: src > > Committed By: pooka > > Date: Fri Dec 31 18:16:41 UTC 2010 > > > > Modified Files: > > src/tests/fs/common: h_fsmacros.h > > > > Log Message: > > Introduce r/o tests. They do two mounts: the first one is r/w and > > runs a generator which primes the fs. The second one is r/o and > > does the actual testing. Also, introduce a nfsro fstype which does > > a clientside r/w mount for a r/o server export. > > > > requested by yamt > > > > (one nfsro test currently fails with EROFS vs. EACCES. Hopefully > > someone else can debate the correct errno) > > >From what I remember of the NFS protocol, the following 'rules' applied: > 1) If you export part of a filesystem, you export all of the filesystem. > 2) If you give anyone access, you give everyone access. > 3) If you give anyone write access, you give everyone write access. > This is all because it is the 'mount' protocol that verifies whether > a client has access - so a client that disobeys the mount protocol, or > fakes up valid nfs file handles can avoid the access checks. > > It is possible that netbsd's nfs server does additional checks but > they are expensive to do on every nfs request.
That's good advise to someone who is configuring an nfs server. -- älä karot toivorikkauttas, kyl rätei ja lumpui piisaa