From: "Paul E. McKenney" <paulmck@kernel.org>
To: Christoph Bartoschek <bartoschek@google.com>
Cc: Chris Mason <clm@fb.com>, Giuseppe Scrivano <gscrivan@redhat.com>,
linux-kernel@vger.kernel.org,
"riel@surriel.com" <riel@surriel.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH RFC fs/namespace] Make kern_unmount() use synchronize_rcu_expedited()
Date: Tue, 26 Apr 2022 16:11:00 -0700 [thread overview]
Message-ID: <20220426231100.GL4285@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <CAAQBG5jnvSxcjwr+L5nuxwh87bv=D=tzU325W2Zp3DVpn-VmcQ@mail.gmail.com>
On Wed, Apr 27, 2022 at 12:58:34AM +0200, Christoph Bartoschek wrote:
> > 3. https://lore.kernel.org/lkml/20220218183114.2867528-1-riel@surriel.com/
> > Refined queue_rcu_work() approach.
> >
> > #1 should work, but the resulting IPIs are not going to make the real-time
> > guys happy. #2 and #3 have been subject to reasonably heavy testing
> > and did fix a very similar issue to the one that you are reporting,
> > but last I knew there were doubts about the concurrency consequences.
> >
> > Could you please give at least #3 a shot and see if it helps you?
>
> I have tried #3 and it works well with my testcases as far as I can see it.
Thank you for giving it a try!
Al, are further adjustments needed to make this patch cover all the
corner cases?
Thanx, Paul
next prev parent reply other threads:[~2022-04-26 23:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 19:05 [PATCH RFC fs/namespace] Make kern_unmount() use synchronize_rcu_expedited() Paul E. McKenney
2022-02-14 19:26 ` Chris Mason
2022-02-14 19:44 ` Paul E. McKenney
2022-02-14 20:55 ` Rik van Riel
2022-02-14 21:41 ` Paul E. McKenney
2022-02-15 18:28 ` Chris Mason
2022-04-26 6:59 ` Christoph Bartoschek
2022-04-26 14:09 ` Paul E. McKenney
2022-04-26 22:58 ` Christoph Bartoschek
2022-04-26 23:11 ` Paul E. McKenney [this message]
2022-04-27 12:19 ` Chris Mason
2022-04-27 15:01 ` Paul E. McKenney
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=20220426231100.GL4285@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=bartoschek@google.com \
--cc=clm@fb.com \
--cc=gscrivan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@surriel.com \
--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).