linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	mingo@redhat.com, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
	rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
	linux-kernel@vger.kernel.org
Subject: Re: BUG: kernel NULL pointer dereference from check_preempt_wakeup()
Date: Mon, 15 Jun 2020 10:29:49 +0200	[thread overview]
Message-ID: <20200615082949.GL2497@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200613234030.GA25146@paulmck-ThinkPad-P72>

On Sat, Jun 13, 2020 at 04:40:30PM -0700, Paul E. McKenney wrote:

> So Peter's patch is fully in the clear:
> 
> Tested-by: Paul E. McKenney <paulmck@kernel.org>

Awesome!, now I get to explain how the lack of that leads to the
observed NULL pointer :-)


      reply	other threads:[~2020-06-15  8:30 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
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 [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=20200615082949.GL2497@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;
as well as URLs for NNTP newsgroup(s).