From: Peter Zijlstra <peterz@infradead.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: BUG: kernel NULL pointer dereference from check_preempt_wakeup()
Date: Fri, 5 Jun 2020 12:56:14 +0200 [thread overview]
Message-ID: <20200605105614.GC2948@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200605103859.GI3976@hirez.programming.kicks-ass.net>
On Fri, Jun 05, 2020 at 12:38:59PM +0200, Peter Zijlstra wrote:
> On Thu, Jun 04, 2020 at 03:54:45PM -0700, Paul E. McKenney wrote:
> > Hello!
> >
> > I get the splat below at a rate of roughly two per thirty hours when
> > running rcutorture scenario TREE03 on x86 at the June 3rd mainline commit:
> >
> > cb8e59cc8720 ("Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next")
> >
> > Running 140 hours of this same scenario at the following June 2nd mainline
> > commit shows no errors:
> >
> > d9afbb350990 ("Merge branch 'next-general' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security")
> >
> > I have started a bisection, but it is likely to take several days to
> > complete. I am looking at ways of speeding this up, but in the meantime,
> > I figured that I should check to see if others are also encountering this.
> >
> > Thoughts?
>
> I think this shows there's a boo-boo with the IPI patches. I've not
> managed to reproduce, but I'll give them another hard look.
>
> Would you have a .config for me? My compiler's check_preempt_wakeup
> isn't anywhere near 0x180 bytes long. I'm thiknig you have
> instrumentation enabled, KCSAN?
n/m, I was looking at the wrong function.. let me go puzzle.
next prev parent reply other threads:[~2020-06-05 10:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 22:54 BUG: kernel NULL pointer dereference from check_preempt_wakeup() Paul E. McKenney
2020-06-05 10:38 ` Peter Zijlstra
2020-06-05 10:56 ` Peter Zijlstra [this message]
2020-06-05 13:14 ` Peter Zijlstra
2020-06-05 14:16 ` Paul E. McKenney
2020-06-05 18:41 ` Paul E. McKenney
[not found] ` <20200606005126.GA21507@paulmck-ThinkPad-P72>
2020-06-06 17:29 ` Paul E. McKenney
2020-06-07 18:57 ` Paul E. McKenney
2020-06-09 15:40 ` Paul E. McKenney
2020-06-13 2:48 ` Paul E. McKenney
2020-06-13 7:26 ` Thomas Gleixner
2020-06-13 14:57 ` Paul E. McKenney
2020-06-13 23:40 ` Paul E. McKenney
2020-06-15 8:29 ` Peter Zijlstra
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=20200605105614.GC2948@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.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