From: Guillaume Morin <guillaume@morinfr.org>
To: "Paul E. McKenney" <paulmck@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: call_rcu data race patch
Date: Mon, 27 Sep 2021 17:38:42 +0200 [thread overview]
Message-ID: <20210927153842.GA12620@bender.morinfr.org> (raw)
In-Reply-To: <20210922192448.GB880162@paulmck-ThinkPad-P17-Gen-1>
On 22 Sep 12:24, Paul E. McKenney wrote:
> On Wed, Sep 22, 2021 at 09:14:07PM +0200, Guillaume Morin wrote:
> > I am little afraid of jinxing it :) but so far so good. I have the a
> > patched kernel running on a few machines (including my most "reliable
> > crasher") and they've been stable so far.
> >
> > It's definitely too early to declare victory though. I will keep you
> > posted.
>
> Here is hoping! ;-)
Things are still stable. So I am pretty optimistic. How are you planning
to proceeed?
The first patch is already in your rcu tree and my gut feeling is that
it is the one that fixes the issue but you're the expert here... Though
I think it should be probably fast tracked and marked for stable?
Are you planning on committing the 2nd patch to your tree?
--
Guillaume Morin <guillaume@morinfr.org>
next prev parent reply other threads:[~2021-09-27 15:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210917191555.GA2198@bender.morinfr.org>
2021-09-17 21:11 ` call_rcu data race patch Paul E. McKenney
2021-09-17 21:34 ` Guillaume Morin
2021-09-17 22:07 ` Paul E. McKenney
2021-09-18 0:39 ` Guillaume Morin
2021-09-18 4:00 ` Paul E. McKenney
2021-09-18 7:08 ` Guillaume Morin
2021-09-19 16:35 ` Paul E. McKenney
2021-09-20 16:05 ` Guillaume Morin
2021-09-22 19:14 ` Guillaume Morin
2021-09-22 19:24 ` Paul E. McKenney
2021-09-27 15:38 ` Guillaume Morin [this message]
2021-09-27 16:10 ` Paul E. McKenney
2021-09-27 16:49 ` Guillaume Morin
2021-09-27 21:46 ` Paul E. McKenney
2021-09-30 13:50 ` Guillaume Morin
2021-11-18 18:41 ` Daniel Vacek
2021-11-18 22:59 ` 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=20210927153842.GA12620@bender.morinfr.org \
--to=guillaume@morinfr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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