From: John Bazik <john_bazik@brown.edu>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: access(2) inaccurately reports execute permissions
Date: Wed, 8 Mar 2017 18:16:03 -0500 [thread overview]
Message-ID: <20170308231602.GR27384@cs.brown.edu> (raw)
In-Reply-To: <20170308220723.GA4902@fieldses.org>
> I hate to say this, but I think there have been some relevant changes
> since then, is it possible to retry with a more recent kernel?
If it's fixed, that's great. I won't be able to try a newer kernel for
a while.
> - watch the traffic in wireshark, check that the ACCESS calls on
> the wire agree with what your test program is seeing.
Looks like the server response is OK:
NFS 234 V4 Reply (Call In 36) ACCESS, [Access Denied: MD XT], [Allowed: RD XE]
> - to verify that your server is mapping to the correct user, try
> touching a new file after su'ing and acquiring kerberos
> credentials, and check who the new file is owned by.
root@radio:/testmnt# ./runas -k test314 touch tmp/foobar
root@radio:/testmnt# ls -l tmp/foobar
-rw-rw---- 1 test314 user-test314 0 Mar 8 18:14 tmp/foobar
John
prev parent reply other threads:[~2017-03-08 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 21:50 access(2) inaccurately reports execute permissions John Bazik
2017-03-08 22:07 ` J. Bruce Fields
2017-03-08 23:16 ` John Bazik [this message]
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=20170308231602.GR27384@cs.brown.edu \
--to=john_bazik@brown.edu \
--cc=bfields@fieldses.org \
--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;
as well as URLs for NNTP newsgroup(s).