From: Frank van Maarseveen <frankvm@frankvm.com>
To: Linux NFS mailing list <linux-nfs@vger.kernel.org>
Subject: V3 ACCESS call fails after server reboot
Date: Mon, 10 Dec 2007 18:20:04 +0100 [thread overview]
Message-ID: <20071210172004.GA8094@janus> (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
. ..
$
--
Frank
next reply other threads:[~2007-12-10 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 17:20 Frank van Maarseveen [this message]
2007-12-10 17:41 ` V3 ACCESS call fails after server reboot J. Bruce Fields
2007-12-10 18:17 ` Frank van Maarseveen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071210172004.GA8094@janus \
--to=frankvm@frankvm.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox