From: Linus Torvalds <torvalds@linux-foundation.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 17/17] RCU'd vfsmounts
Date: Thu, 3 Oct 2013 12:06:04 -0700 [thread overview]
Message-ID: <CA+55aFy5kA7ubyetouWsB0OnB5mMRAoyQ-4kbQsCVWARFaf9MA@mail.gmail.com> (raw)
In-Reply-To: <20131003174439.GG13318@ZenIV.linux.org.uk>
On Thu, Oct 3, 2013 at 10:44 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> Anyway, I've done nicer variants of that protection for everything except
> fuse (hadn't gotten around to it yet); see vfs.git#experimental now:
Ok, I did a quick test, and it looks ok here, so looking good for 3.13.
However, the new smp_mb() in mntput_no_expire() is quite noticeable in
the path lookup stress-test profiles. And I'm not seeing what that
allegedly protects against, especially if mnt_ns is NULL (ie all the
common important cases).
Linus
next prev parent reply other threads:[~2013-10-03 19:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 6:20 [PATCH 17/17] RCU'd vfsmounts Al Viro
[not found] ` <CA+55aFzeDP6J4ekdn4-85yoXzX3xmEp_qc3npvqepJM+MFn=6Q@mail.gmail.com>
[not found] ` <20131003105130.GE13318@ZenIV.linux.org.uk>
[not found] ` <CA+55aFzh+n_2fs=aWcT_5gnLC_pWSHqQPJeQ+fg=+Xw7ib9=dQ@mail.gmail.com>
[not found] ` <20131003174439.GG13318@ZenIV.linux.org.uk>
2013-10-03 19:06 ` Linus Torvalds [this message]
2013-10-03 19:43 ` Al Viro
2013-10-03 20:19 ` Linus Torvalds
2013-10-03 20:41 ` Al Viro
2013-10-03 20:52 ` Linus Torvalds
2013-10-03 21:14 ` Al Viro
2013-10-04 2:53 ` Al Viro
2013-10-04 8:37 ` Christoph Hellwig
2013-10-04 12:58 ` Al Viro
2013-10-04 14:00 ` Christoph Hellwig
2013-10-03 23:28 ` Josh Triplett
2013-10-03 23:51 ` Linus Torvalds
2013-10-04 0:41 ` Josh Triplett
2013-10-04 0:45 ` Linus Torvalds
2013-10-04 6:41 ` Ingo Molnar
2013-10-04 5:29 ` Paul E. McKenney
2013-10-04 6:03 ` Josh Triplett
2013-10-04 6:15 ` Paul E. McKenney
2013-10-04 7:04 ` Josh Triplett
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=CA+55aFy5kA7ubyetouWsB0OnB5mMRAoyQ-4kbQsCVWARFaf9MA@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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).