From: Steven Rostedt <rostedt@goodmis.org>
To: Zhouyi Zhou <zhouzhouyi@gmail.com>
Cc: Joel Fernandes <joel@joelfernandes.org>,
Sanan Hasanov <sanan.hasanov@knights.ucf.edu>,
paulmck@kernel.org, frederic@kernel.org,
quic_neeraju@quicinc.com, josh@joshtriplett.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller@googlegroups.com, contact@pgazz.com
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in rcu_core
Date: Mon, 27 Feb 2023 11:16:26 -0500 [thread overview]
Message-ID: <20230227111626.463b8f85@gandalf.local.home> (raw)
In-Reply-To: <CAABZP2zZHQ22MPsWkPZ5kPW5SNDPt0mT37xw3f4VNLeBsxRPvw@mail.gmail.com>
On Tue, 28 Feb 2023 00:11:51 +0800
Zhouyi Zhou <zhouzhouyi@gmail.com> wrote:
> > Yes certainly, the rcu_head is allocated on the caller side so it
> > could have been trampled while the callback was still in flight.
> Thank you all for your guidance, I learned a lot during this process
> >
> > > OR it could be a bug with RCU if the synchronize_rcu() ended before the
> > > grace periods have finished.
> Thanks again.
>
> By the way, the syzkaller on my local machine has been running for 8
> hours, only three bugs reported[1][2][3], but they don't seem to be
> related to Sanan's original report.
> Maybe there are some configuration mismatches between us.The test
> continues, I will report to you once I have any new discovery.
Note, the above races (either bug, the one that tramples on something in
RCU flight, or a synchronize_sched() returning early) may be extremely hard
to hit. It could have been the planets were lined up just right to hit the
bug, and won't happen for another 27,000 years.
-- Steve
next prev parent reply other threads:[~2023-02-27 16:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 6:23 Sanan Hasanov
2023-02-27 8:02 ` Zhouyi Zhou
2023-02-27 13:15 ` Joel Fernandes
2023-02-27 14:59 ` Paul E. McKenney
2023-02-27 15:13 ` Joel Fernandes
2023-02-27 15:32 ` Steven Rostedt
2023-02-27 15:48 ` Joel Fernandes
2023-02-27 16:11 ` Zhouyi Zhou
2023-02-27 16:16 ` Steven Rostedt [this message]
2023-02-27 16:32 ` Paul E. McKenney
2023-02-28 7:58 ` Zhouyi Zhou
2023-02-28 8:55 ` Zhuo, Qiuxu
2023-02-28 23:51 ` 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=20230227111626.463b8f85@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=contact@pgazz.com \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=sanan.hasanov@knights.ucf.edu \
--cc=syzkaller@googlegroups.com \
--cc=zhouzhouyi@gmail.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
all inboxes | Powered by JetHome®