From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Trond Myklebust <trondmy@primarydata.com>
Cc: Schumaker Anna <anna.schumaker@netapp.com>,
List Linux NFS Mailing <linux-nfs@vger.kernel.org>
Subject: Re: 4.8-rcN nfs, access(W_OK) on an immutable inode
Date: Tue, 06 Sep 2016 03:55:49 +0900 [thread overview]
Message-ID: <27139.1473101749@jrobl> (raw)
In-Reply-To: <D2C9D52A-1C3D-491E-9C90-205B2B85F284@primarydata.com>
Trond Myklebust:
> The NFS protocol has no way to convey to the client that the inode is label=
> ed as immutable on the server. The NFSv4.1 =93retention_hold=94 mechanism d=
> escribed in RFC5661 comes close, and could possibly be used, but it is not =
> implemented for now.
>
> Note also that file immutability is not a POSIX concept, and EPERM is conse=
> quently not listed as one of the POSIX sanctioned return values for access(=
> ): http://pubs.opengroup.org/onlinepubs/9699919799/functions/access.html
Ok.
Thanx for the explanation.
J. R. Okajima
prev parent reply other threads:[~2016-09-05 18:55 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 ` 4.8-rcN nfs, access(W_OK) on an immutable inode J. R. Okajima
2016-09-05 17:59 ` Trond Myklebust
2016-09-05 18:55 ` J. R. Okajima [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=27139.1473101749@jrobl \
--to=hooanon05g@gmail.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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 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.