linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. R. Okajima" <hooanon05g@gmail.com>
To: trond.myklebust@primarydata.com, anna.schumaker@netapp.com,
	linux-nfs@vger.kernel.org
Subject: 4.8-rcN nfs, access(W_OK) on an immutable inode
Date: Tue, 06 Sep 2016 02:19:57 +0900	[thread overview]
Message-ID: <24930.1473095997@jrobl> (raw)
In-Reply-To: <3647.1472877116@jrobl>


Hello again,

linux-v4.8-rcN has a commit
	337684a 2016-08-07 fs: return EPERM on immutable inode

I am afraid NFS should follow the same behaviour. In other words,
fs/nfs/dir.c:nfs_do_access() should return -EPERM when MAY_WRITE on an
immutable inode. Currently it returns EACCES.


J. R. Okajima

  parent reply	other threads:[~2016-09-05 17:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-03  4:31 4.8-rcN nfs O_DYSNC, write(2) doesn't return ENOSPC J. R. Okajima
2016-09-03 16:13 ` Trond Myklebust
2016-09-04 18:58   ` J. R. Okajima
2016-09-05 17:19 ` J. R. Okajima [this message]
2016-09-05 17:59   ` 4.8-rcN nfs, access(W_OK) on an immutable inode Trond Myklebust
2016-09-05 18:55     ` J. R. Okajima

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=24930.1473095997@jrobl \
    --to=hooanon05g@gmail.com \
    --cc=anna.schumaker@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.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 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).