From: "J. Bruce Fields" <bfields@fieldses.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC][PATCH] nfsd regression since delayed fput()
Date: Thu, 17 Oct 2013 14:14:57 -0400 [thread overview]
Message-ID: <20131017181457.GA6987@fieldses.org> (raw)
In-Reply-To: <CA+55aFyjNJeXMOksMS0CdW-_KejH5KfD=CzMMew+mtd8y7J7sA@mail.gmail.com>
On Wed, Oct 16, 2013 at 09:48:06PM -0700, Linus Torvalds wrote:
> On Wed, Oct 16, 2013 at 11:52 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > If anybody has better ideas, I'll gladly take those instead - this
> > approach feels kludgy ;-/
>
> It looks kludgy indeed, but I do like the concept of basically
> rate-limiting delayed_fput_work.
>
> At the same time, I worry that it will cause the same kinds of things
> that we discussed for user processes: delayed fput can result in
> visible semantic differences (eg silly-renames) if it is delayed past
> other operations that care about elevated reference counts.
>
> Now I hope that people don't nfs-(re)export nfs filesystems, so the
> nfs silly-rename isn't necessarily an issue, but I could imagine other
> similar things.
NFS isn't exportable and there aren't any plans to change that.
--b.
next prev parent reply other threads:[~2013-10-17 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 18:52 [RFC][PATCH] nfsd regression since delayed fput() Al Viro
2013-10-17 4:48 ` Linus Torvalds
2013-10-17 18:14 ` J. Bruce Fields [this message]
2013-10-17 18:29 ` Linus Torvalds
2013-10-17 18:39 ` Al Viro
2013-10-17 19:09 ` Linus Torvalds
2013-10-17 20:12 ` Al Viro
2013-10-17 22:33 ` Linus Torvalds
2013-10-25 14:18 ` Al Viro
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=20131017181457.GA6987@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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.