From: Joel Fernandes <joel@joelfernandes.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>,
Amol Grover <frextrite@gmail.com>,
linux-kernel@vger.kernel.org, philip.li@intel.com
Subject: Re: db4ead2cd5 ("Default enable RCU list lockdep debugging with .."): WARNING: suspicious RCU usage
Date: Mon, 6 Apr 2020 12:01:38 -0400 [thread overview]
Message-ID: <20200406160138.GJ83565@google.com> (raw)
In-Reply-To: <20200406153237.GF19865@paulmck-ThinkPad-P72>
On Mon, Apr 06, 2020 at 08:32:37AM -0700, Paul E. McKenney wrote:
> On Mon, Apr 06, 2020 at 11:22:59AM -0400, Joel Fernandes wrote:
> > On Mon, Apr 06, 2020 at 08:20:57AM +0530, Madhuparna Bhowmik wrote:
> > > On Sun, Apr 05, 2020 at 07:52:32AM -0700, Paul E. McKenney wrote:
> > > > On Sun, Apr 05, 2020 at 06:10:31PM +0800, kernel test robot wrote:
> > > > > Greetings,
> > > > >
> > > > > 0day kernel testing robot got the below dmesg and the first bad commit is
> > > > >
> > > > > https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2020.03.21a
> > > >
> > > > Is some of the required conversion still left to be done? Or on its
> > > > way up some other tree?
> > > >
> > > > If either of these two, my normal approach would be to hold this commit
> > > > back in order to give the fixes time to hit mainline.
> > > >
> > > > But either way, please let me know!
> > > >
> > > Yes, some of the patches are not yet reviewed by maintainers and we will
> > > resend them. Also, this report reports a few new ones that we haven't
> > > fixed yet (need some help from maintainers to do so).
> > > We are working on fixing them. May be holding the commit is a
> > > good idea.
> >
> > I am Ok with holding on to the commit for mainline. But I would like it into
> > linux-next so that we and others can get some more velocity on fixing the
> > remaining issues (and any maintainers who have not yet accepted patches to
> > review those). We fixed most of them but there could be some more lurking.
> > Paul, how does that sound?
>
> Once v5.7-rc1 comes out, it sounds great!
>
> (Just got my knuckles rapped (gently) for forgetting to pull this stuff
> out of -next for all of last week.)
>
> So early next week it returns to -next.
Perfect, thanks!
- Joel
next prev parent reply other threads:[~2020-04-06 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 10:10 db4ead2cd5 ("Default enable RCU list lockdep debugging with .."): WARNING: suspicious RCU usage kernel test robot
2020-04-05 14:52 ` Paul E. McKenney
2020-04-06 2:50 ` Madhuparna Bhowmik
2020-04-06 15:22 ` Joel Fernandes
2020-04-06 15:32 ` Paul E. McKenney
2020-04-06 16:01 ` Joel Fernandes [this message]
2020-04-06 13:56 ` Joel Fernandes
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=20200406160138.GJ83565@google.com \
--to=joel@joelfernandes.org \
--cc=frextrite@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=madhuparnabhowmik10@gmail.com \
--cc=paulmck@kernel.org \
--cc=philip.li@intel.com \
/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