Skip to contentSkip to conversation

V3 ACCESS call fails after server reboot

DISCUSSION Frank van Maarseveen 2 participants 3 messages Dec 10, 2007

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Tested on 2.6.22.10 and 2.6.23.9, client and server running same version. export options: rw,sync,no_root_squash,no_subtree_check,mp

After a substantial amount of time (days) but also after a server reboot a process loses access to its current working directory when access to a parent directory two (or more) levels up has been revoked:

	$ cd /mnt
	$ mkdir -p a/b/c
	$ cd a/b/c
	$ chmod 0 ../..
	$ ls -a
	. ..
	$
		(wait a loong time or reboot server)
	$ ls -a
	ls: .: Permission denied

Network traffic capture showed a V3 ACCESS call for above "." failing on the server after the reboot with NFS3ERR_ACCES. It succeeded before.

I have the impression the server is internally rechecking the entire path when its caches have been flushed. This behavior is problematic for daemons which change uid, for example.

Note on a different (client) issue: Trying the above with the direct parent (i.e. chmod 0 ..) fails with ESTALE due to lookup of "c" in "b" to which access has been revoked (no reboot needed):

	$ mkdir -p a/b/c
	$ cd a/b/c
	$ chmod 0 ..
	$ ls -a
	ls: .: Stale NFS file handle
	$ chmod 755 ..
	$ ls -a
	.  ..
	$
Signature · 1 line
Frank
#1 lore raw
Quoted 18 lines · Frank van Maarseveen

Tested on 2.6.22.10 and 2.6.23.9, client and server running same version. export options: rw,sync,no_root_squash,no_subtree_check,mp

After a substantial amount of time (days) but also after a server reboot a process loses access to its current working directory when access to a parent directory two (or more) levels up has been revoked:

	$ cd /mnt
	$ mkdir -p a/b/c
	$ cd a/b/c
	$ chmod 0 ../..
	$ ls -a
	. ..
	$
		(wait a loong time or reboot server)
	$ ls -a
	ls: .: Permission denied
Quoted 6 lines

Network traffic capture showed a V3 ACCESS call for above "." failing on the server after the reboot with NFS3ERR_ACCES. It succeeded before.

I have the impression the server is internally rechecking the entire path when its caches have been flushed. This behavior is problematic for daemons which change uid, for example.

What are your export options? (Do you have nosubtreecheck turned on?)

--b.

Quoted 20 lines

Note on a different (client) issue: Trying the above with the direct parent (i.e. chmod 0 ..) fails with ESTALE due to lookup of "c" in "b" to which access has been revoked (no reboot needed):

	$ mkdir -p a/b/c
	$ cd a/b/c
	$ chmod 0 ..
	$ ls -a
	ls: .: Stale NFS file handle
	$ chmod 755 ..
	$ ls -a
	.  ..
	$
Signature · 5 lines
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#2 lore raw
Quoted 19 lines · J. Bruce Fields
Quoted 18 lines · Frank van Maarseveen

Tested on 2.6.22.10 and 2.6.23.9, client and server running same version. export options: rw,sync,no_root_squash,no_subtree_check,mp

After a substantial amount of time (days) but also after a server reboot a process loses access to its current working directory when access to a parent directory two (or more) levels up has been revoked:

	$ cd /mnt
	$ mkdir -p a/b/c
	$ cd a/b/c
	$ chmod 0 ../..
	$ ls -a
	. ..
	$
		(wait a loong time or reboot server)
	$ ls -a
	ls: .: Permission denied
Quoted 8 lines
Quoted 6 lines

Network traffic capture showed a V3 ACCESS call for above "." failing on the server after the reboot with NFS3ERR_ACCES. It succeeded before.

I have the impression the server is internally rechecking the entire path when its caches have been flushed. This behavior is problematic for daemons which change uid, for example.

What are your export options? (Do you have nosubtreecheck turned on?)

yes, see above export options.

Signature · 1 line
Frank