From: peterz@infradead.org
To: Qian Cai <cai@redhat.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
rcu@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, Linux PM <linux-pm@vger.kernel.org>,
": Paul E. McKenney" <paulmck@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Will Deacon <will@kernel.org>, Guenter Roeck <linux@roeck-us.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Steven Rostedt <rostedt@goodmis.org>,
Juri Lelli <juri.lelli@redhat.com>
Subject: Re: WARNING: suspicious RCU usage: race/events/tlb.h:57 suspicious rcu_dereference_check() usage!
Date: Tue, 15 Sep 2020 12:35:39 +0200 [thread overview]
Message-ID: <20200915103539.GW1362448@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <d7bdc37f6e3f98379289b262aea812e1894cd69b.camel@redhat.com>
On Mon, Sep 14, 2020 at 01:29:34PM -0400, Qian Cai wrote:
> On Wed, 2020-09-09 at 10:08 +0530, Naresh Kamboju wrote:
> > While booting x86_64 with Linux next 20200908 tag kernel this warning
> > was noticed.
>
> This pretty much looks like the same issue in:
>
> https://lore.kernel.org/lkml/20200902035146.GA45826@roeck-us.net/
>
> Can you revert the patchset to see if it is related?
Don't bother.. I'll be sending patches soon.
prev parent reply other threads:[~2020-09-15 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 4:38 WARNING: suspicious RCU usage: race/events/tlb.h:57 suspicious rcu_dereference_check() usage! Naresh Kamboju
2020-09-14 17:29 ` Qian Cai
2020-09-15 10:35 ` peterz [this message]
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=20200915103539.GW1362448@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=cai@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).