All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Valdis.Kletnieks@vt.edu
Cc: sachinp <sachinp@linux.vnet.ibm.com>,
	Li Zefan <lizf@cn.fujitsu.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linuxppc-dev <Linuxppc-dev@ozlabs.org>,
	paulmck@linux.vnet.ibm.com,
	Subrata Modak <subrata@linux.vnet.ibm.com>,
	DIVYA PRAKASH <dipraksh@linux.vnet.ibm.com>
Subject: Re: 2.6.35-stable/ppc64/p7: suspicious rcu_dereference_check() usage detected during 2.6.35-stable boot
Date: Thu, 16 Sep 2010 17:50:48 +0200	[thread overview]
Message-ID: <1284652248.2275.570.camel@laptop> (raw)
In-Reply-To: <10430.1284649951@localhost>

On Thu, 2010-09-16 at 11:12 -0400, Valdis.Kletnieks@vt.edu wrote:
>=20
> Ping?  I just hit it on 2.6.36-rc4-mmotm0915.  Just wanted to make sure t=
he
> issue hadn't been lost/forgotten.=20

lost,.. thanks!

WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Valdis.Kletnieks@vt.edu
Cc: paulmck@linux.vnet.ibm.com,
	Subrata Modak <subrata@linux.vnet.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Li Zefan <lizf@cn.fujitsu.com>,
	Linuxppc-dev <Linuxppc-dev@ozlabs.org>,
	sachinp <sachinp@linux.vnet.ibm.com>,
	DIVYA PRAKASH <dipraksh@linux.vnet.ibm.com>
Subject: Re: 2.6.35-stable/ppc64/p7: suspicious rcu_dereference_check() usage detected during 2.6.35-stable boot
Date: Thu, 16 Sep 2010 17:50:48 +0200	[thread overview]
Message-ID: <1284652248.2275.570.camel@laptop> (raw)
In-Reply-To: <10430.1284649951@localhost>

On Thu, 2010-09-16 at 11:12 -0400, Valdis.Kletnieks@vt.edu wrote:
> 
> Ping?  I just hit it on 2.6.36-rc4-mmotm0915.  Just wanted to make sure the
> issue hadn't been lost/forgotten. 

lost,.. thanks!

  reply	other threads:[~2010-09-16 15:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02  8:52 2.6.35-stable/ppc64/p7: suspicious rcu_dereference_check() usage detected during 2.6.35-stable boot Subrata Modak
2010-08-02  8:52 ` Subrata Modak
2010-08-04 14:56 ` Subrata Modak
2010-08-04 14:56   ` Subrata Modak
2010-08-09 16:12 ` Paul E. McKenney
2010-08-09 16:12   ` Paul E. McKenney
2010-08-13  6:55   ` Subrata Modak
2010-08-13  6:55     ` Subrata Modak
     [not found]     ` <1281682514.5976.2.camel-NRFfyExJdYpgXGGE5LP+UZlqa2bBAFbm0E9HWUfgJXw@public.gmane.org>
2010-08-13  7:42       ` Dhaval Giani
2010-08-13  7:42     ` Dhaval Giani
2010-08-13  7:42       ` Dhaval Giani
2010-08-13  8:37   ` Subrata Modak
2010-08-13  8:37     ` Subrata Modak
     [not found]   ` <20100809161200.GC3026-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2010-08-13  8:37     ` Subrata Modak
2010-09-16 15:12   ` Valdis.Kletnieks
2010-09-16 15:12     ` Valdis.Kletnieks
2010-09-16 15:50     ` Peter Zijlstra [this message]
2010-09-16 15:50       ` Peter Zijlstra
2010-09-16 15:50   ` Peter Zijlstra
2010-09-16 15:50     ` Peter Zijlstra
2010-09-16 16:12     ` Paul E. McKenney
2010-09-16 16:12       ` Paul E. McKenney
2010-09-16 18:19       ` Subrata Modak
2010-09-16 18:19         ` Subrata Modak

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=1284652248.2275.570.camel@laptop \
    --to=peterz@infradead.org \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=dipraksh@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=sachinp@linux.vnet.ibm.com \
    --cc=subrata@linux.vnet.ibm.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.