From: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: expected unxpected behavior
Date: Wed, 22 May 2013 11:58:26 +0200 (CEST) [thread overview]
Message-ID: <2007295634.1529248.1369216706282.JavaMail.root@desy.de> (raw)
In-Reply-To: <1164976622.1510880.1369209469446.JavaMail.root@desy.de>
Hi,
we hit some strange behavior which is expected from one side, but unexpected at the same time.
We run our nfs server with v3 and v4. Due to misconfiguration in idmapping, we got some files
to be owned by uid -1. Which is ok, as with v4 server returns nobody. Nevertheless, this
prevent to list the directory with v3. This is the result of uid_valid()/gid_valid() calls
in nfs3xdr.c:decode_fattr3. The uid_valid/gid_valid checks that provided uid/gid are not -1.
Probably this is ok. My confusion is: a) one file with bad uid/gid prevents listing of a
directory, b) in nfs v3 spec uid3 (as well as uid_t in linux) is unsigned int 32 and
value 0xffffffff is absolutely valid.
Tigran.
next parent reply other threads:[~2013-05-22 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1164976622.1510880.1369209469446.JavaMail.root@desy.de>
2013-05-22 9:58 ` Mkrtchyan, Tigran [this message]
2013-05-22 13:56 ` expected unxpected behavior Myklebust, Trond
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=2007295634.1529248.1369216706282.JavaMail.root@desy.de \
--to=tigran.mkrtchyan@desy.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.