From: "J. Bruce Fields" <bfields@fieldses.org>
To: Dilip Kumar <udilipkumar@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Bug in NFSV3 ACCESS Procedure reply
Date: Thu, 28 Aug 2008 14:54:25 -0400 [thread overview]
Message-ID: <20080828185425.GA6146@fieldses.org> (raw)
In-Reply-To: <9344d2ec0808281052s71efeeebh81fea6805b6eef10-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, Aug 28, 2008 at 10:52:07AM -0700, Dilip Kumar wrote:
> Do you see this issue on your version too? Not sure if there is a
> patch already addressing this issue.
Hm. It looks like it may just be this:
static struct accessmap nfs3_diraccess[] = {
{ NFS3_ACCESS_READ, MAY_READ },
{ NFS3_ACCESS_LOOKUP, MAY_EXEC },
{ NFS3_ACCESS_MODIFY, MAY_EXEC|MAY_WRITE|MAY_TRUNC },
{ NFS3_ACCESS_EXTEND, MAY_EXEC|MAY_WRITE },
{ NFS3_ACCESS_DELETE, MAY_REMOVE },
{ 0, 0 }
};
So it doesn't claim write is allowed unless exec is also allowed.
I think that's actually how the local filesystem behaves--is there
any operation you can do locally with only write permissions?
Why is this behavior a problem for you, anyway?
--b.
next prev parent reply other threads:[~2008-08-28 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 19:41 Bug in NFSV3 ACCESS Procedure reply Dilip Kumar
[not found] ` <9344d2ec0808271241x375a4d86r6cfa7c10beb905c8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-08-28 17:34 ` J. Bruce Fields
2008-08-28 17:41 ` Dilip Kumar
[not found] ` <9344d2ec0808281041w15e2738ew546531398f80a312-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-08-28 17:49 ` J. Bruce Fields
2008-08-28 17:52 ` Dilip Kumar
[not found] ` <9344d2ec0808281052s71efeeebh81fea6805b6eef10-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-08-28 18:54 ` J. Bruce Fields [this message]
2008-08-28 21:22 ` Dilip Kumar
[not found] ` <9344d2ec0808281422v13ed6af9gc0f91569d52ca3be-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-08-29 0:27 ` J. Bruce Fields
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=20080828185425.GA6146@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=udilipkumar@gmail.com \
/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.