From: NeilBrown <neilb@suse.com>
To: Olga Kornievskaia <aglo@umich.edu>, David Howells <dhowells@redhat.com>
Cc: Olga Kornievskaia <kolga@netapp.com>,
"linux-fsdevel\@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
linux-nfs <linux-nfs@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: [RFC v3 0/3] VFS/NFS support to destroy FS credentials
Date: Fri, 11 Aug 2017 16:53:55 +1000 [thread overview]
Message-ID: <8760dur3wc.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <CAN-5tyE11DaCCXdn3y+Q4V+Lyt_UgtzU+JBhwP68gxQc5_v6pQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
On Thu, Aug 10 2017, Olga Kornievskaia wrote:
> On Wed, Aug 9, 2017 at 8:55 AM, David Howells <dhowells@redhat.com> wrote:
>> You may also want to flush any outstanding dirty data and wait for in-progress
>> operations.
>
> Sorry for the delayed response but I've been thinking about it as this
> is a tricky one (for me at least).
>
> Even currently, each file system needs a way to deal with flushing
> cached data to storage in the situation where creds might have expired
> in between when the kernel returned control back to the user but
> before all of buffered writes are flushed. NFS4.1 has wording in the
> spec for using machine credentials in that case.
>
> At the VFS layer, there no what to tell which dirty data belongs to
> which user. Flushing all data under the superblock seems like a bad
> idea?
NFS flushes data when the file descriptor is closed. So as long as the
user does have any open-for-write file descriptors, their data should be
safe. Purging credentials while you still have open-for-write file
descriptors is probably not a good idea.
This is not the case if you "nocto" mount option is used, but that is
recommended only for read-mostly mounts.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-08-11 6:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 21:23 [RFC v3 0/3] VFS/NFS support to destroy FS credentials Olga Kornievskaia
2017-08-07 21:23 ` [RFC v3 1/3] VFS adding destroy_creds call Olga Kornievskaia
2017-08-07 21:23 ` [RFC 1/1] destroy_creds.2: new page documenting destroy_creds() Olga Kornievskaia
2017-08-09 12:30 ` Jeff Layton
2017-08-09 15:45 ` Olga Kornievskaia
2017-08-11 7:17 ` NeilBrown
2017-08-11 11:18 ` Jeff Layton
2017-08-11 14:05 ` Olga Kornievskaia
[not found] ` <E127503D-3DFC-4FD3-99F6-012D100C168B@netapp.com>
2017-08-11 14:22 ` Jeff Layton
2017-08-11 15:12 ` Trond Myklebust
2017-08-13 11:38 ` Jeff Layton
2017-08-14 15:43 ` Olga Kornievskaia
[not found] ` <CB7D102A-5711-4661-928F-3689895A1A5A@netapp.com>
2017-08-14 15:59 ` Jeff Layton
2017-08-11 13:37 ` Olga Kornievskaia
2017-08-11 14:09 ` Olga Kornievskaia
2017-08-09 16:08 ` Andy Lutomirski
2017-08-09 16:44 ` Olga Kornievskaia
2017-08-07 21:23 ` [RFC v3 2/3] SUNRPC mark user credentials destroyed Olga Kornievskaia
2017-08-07 21:23 ` [RFC v3 3/3] NFS define vfs destroy_creds functions Olga Kornievskaia
2017-08-09 12:55 ` [RFC v3 0/3] VFS/NFS support to destroy FS credentials David Howells
2017-08-10 16:52 ` Olga Kornievskaia
2017-08-11 6:53 ` NeilBrown [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=8760dur3wc.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=aglo@umich.edu \
--cc=dhowells@redhat.com \
--cc=kolga@netapp.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.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).