From: Weston Andros Adamson <dros@netapp.com>
To: Trond.Myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] NFSv4: fix corner cases with ACCESS in OPEN
Date: Tue, 2 Oct 2012 14:49:50 -0700 [thread overview]
Message-ID: <1349214592-11717-1-git-send-email-dros@netapp.com> (raw)
My recent "ACCESS in OPEN" patch that fixed permissions due to OPEN operations
having no way to differentiate between READ and EXEC had several issues:
- when files are opened O_EXCL, ACCESS will always return permission denied
for all bits until close is called.
- POSIX allows processes to write to files without write permissions if
that process created the file
next reply other threads:[~2012-10-02 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 21:49 Weston Andros Adamson [this message]
2012-10-02 21:49 ` [PATCH 1/2] NFSv4: don't check MAY_WRITE access bit in OPEN Weston Andros Adamson
2012-10-02 21:49 ` [PATCH 2/2] NFSv4: don't put ACCESS in OPEN compound if O_EXCL Weston Andros Adamson
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=1349214592-11717-1-git-send-email-dros@netapp.com \
--to=dros@netapp.com \
--cc=Trond.Myklebust@netapp.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;
as well as URLs for NNTP newsgroup(s).