All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Christoph Lameter <cl@linux.com>, Jet Chen <jet.chen@intel.com>,
	Su Tao <tao.su@intel.com>, Yuanhan Liu <yuanhan.liu@intel.com>,
	LKP <lkp@01.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [percpu] BUG: unable to handle kernel NULL pointer dereference at (null)
Date: Sat, 13 Sep 2014 20:41:38 +0800	[thread overview]
Message-ID: <20140913124138.GB20185@localhost> (raw)
In-Reply-To: <20140904160428.GE5001@linux.vnet.ibm.com>

On Thu, Sep 04, 2014 at 09:04:28AM -0700, Paul E. McKenney wrote:
> On Thu, Sep 04, 2014 at 08:38:45PM +0800, Fengguang Wu wrote:
> > On Tue, Sep 02, 2014 at 10:16:57AM -0700, Paul E. McKenney wrote:
> > > On Tue, Sep 02, 2014 at 11:55:58AM -0500, Christoph Lameter wrote:
> > > > On Tue, 2 Sep 2014, Paul E. McKenney wrote:
> > > > 
> > > > > Added by ac1bea85781e (sched,rcu: Make cond_resched() report RCU quiescent
> > > > > states), removed by 4a81e8328d379 (rcu: Reduce overhead of cond_resched()
> > > > > checks for RCU).  So, as you say, no effect on contemporary kernels.
> > > > 
> > > > Well not sure what to make out of all of this....
> > > 
> > > Yep, still confused as to how the patch adding the definition could have
> > > caused a failure.  Fengguang, any thoughts?
> > 
> > Yeah this is confusing.. I checked carefully and find that commit
> > 0e98023 and afea227 are built on 2 quite different servers -- which
> > might generate slightly different code. I'll fix this issue and make
> > the build server selection more consistent.
> 
> Looking forward to seeing what shows up!

The new bisect catches commit 945fa9c631b04febe295a3a2a00c7e4a3cfb97db
("torture: Dump ftrace buffer when the RCU grace period stalls"). I
just reported it in another email.

Thanks,
Fengguang

WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: lkp@lists.01.org
Subject: Re: [percpu] BUG: unable to handle kernel NULL pointer dereference at (null)
Date: Sat, 13 Sep 2014 20:41:38 +0800	[thread overview]
Message-ID: <20140913124138.GB20185@localhost> (raw)
In-Reply-To: <20140904160428.GE5001@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]

On Thu, Sep 04, 2014 at 09:04:28AM -0700, Paul E. McKenney wrote:
> On Thu, Sep 04, 2014 at 08:38:45PM +0800, Fengguang Wu wrote:
> > On Tue, Sep 02, 2014 at 10:16:57AM -0700, Paul E. McKenney wrote:
> > > On Tue, Sep 02, 2014 at 11:55:58AM -0500, Christoph Lameter wrote:
> > > > On Tue, 2 Sep 2014, Paul E. McKenney wrote:
> > > > 
> > > > > Added by ac1bea85781e (sched,rcu: Make cond_resched() report RCU quiescent
> > > > > states), removed by 4a81e8328d379 (rcu: Reduce overhead of cond_resched()
> > > > > checks for RCU).  So, as you say, no effect on contemporary kernels.
> > > > 
> > > > Well not sure what to make out of all of this....
> > > 
> > > Yep, still confused as to how the patch adding the definition could have
> > > caused a failure.  Fengguang, any thoughts?
> > 
> > Yeah this is confusing.. I checked carefully and find that commit
> > 0e98023 and afea227 are built on 2 quite different servers -- which
> > might generate slightly different code. I'll fix this issue and make
> > the build server selection more consistent.
> 
> Looking forward to seeing what shows up!

The new bisect catches commit 945fa9c631b04febe295a3a2a00c7e4a3cfb97db
("torture: Dump ftrace buffer when the RCU grace period stalls"). I
just reported it in another email.

Thanks,
Fengguang

  reply	other threads:[~2014-09-13 12:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02  4:58 [percpu] BUG: unable to handle kernel NULL pointer dereference at (null) Fengguang Wu
2014-09-02  4:58 ` Fengguang Wu
2014-09-02 15:34 ` Paul E. McKenney
2014-09-02 15:34   ` Paul E. McKenney
2014-09-02 16:00   ` Christoph Lameter
2014-09-02 16:00     ` Christoph Lameter
2014-09-02 16:21     ` Paul E. McKenney
2014-09-02 16:21       ` Paul E. McKenney
2014-09-02 16:55       ` Christoph Lameter
2014-09-02 16:55         ` Christoph Lameter
2014-09-02 17:16         ` Paul E. McKenney
2014-09-02 17:16           ` Paul E. McKenney
2014-09-04 12:38           ` Fengguang Wu
2014-09-04 12:38             ` Fengguang Wu
2014-09-04 16:04             ` Paul E. McKenney
2014-09-04 16:04               ` Paul E. McKenney
2014-09-13 12:41               ` Fengguang Wu [this message]
2014-09-13 12:41                 ` Fengguang Wu

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=20140913124138.GB20185@localhost \
    --to=fengguang.wu@intel.com \
    --cc=cl@linux.com \
    --cc=jet.chen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=tao.su@intel.com \
    --cc=yuanhan.liu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.