All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: paulmck@linux.vnet.ibm.com
Cc: sachinp <sachinp@linux.vnet.ibm.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Li Zefan <lizf@cn.fujitsu.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linuxppc-dev <Linuxppc-dev@ozlabs.org>,
	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 11:12:31 -0400	[thread overview]
Message-ID: <10430.1284649951@localhost> (raw)
In-Reply-To: Your message of "Mon, 09 Aug 2010 09:12:00 PDT." <20100809161200.GC3026@linux.vnet.ibm.com>

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

On Mon, 09 Aug 2010 09:12:00 PDT, "Paul E. McKenney" said:
> On Mon, Aug 02, 2010 at 02:22:12PM +0530, Subrata Modak wrote:
> > Hi,
> >
> > The following suspicious rcu_dereference_check() usage is detected
> > during 2.6.35-stable boot on my ppc64/p7 machine:
> >
> > =========================
> > [ INFO: suspicious rcu_dereference_check() usage. ]
> > ---------------------------------------------------
> > kernel/sched.c:616 invoked rcu_dereference_check() without protection!
> > other info that might help us debug this:

> Thank you for locating this one!  This looks like the same issue that
> Ilia Mirkin located.  Please see below for my analysis -- no fix yet,
> as I need confirmation from cgroups experts.  I can easily create a
> patch that suppresses the warning, but I don't yet know whether this is
> the right thing to do.

Ping?  I just hit it on 2.6.36-rc4-mmotm0915.  Just wanted to make sure the
issue hadn't been lost/forgotten.

[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Valdis.Kletnieks@vt.edu
To: paulmck@linux.vnet.ibm.com
Cc: Subrata Modak <subrata@linux.vnet.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	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 11:12:31 -0400	[thread overview]
Message-ID: <10430.1284649951@localhost> (raw)
In-Reply-To: Your message of "Mon, 09 Aug 2010 09:12:00 PDT." <20100809161200.GC3026@linux.vnet.ibm.com>

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

On Mon, 09 Aug 2010 09:12:00 PDT, "Paul E. McKenney" said:
> On Mon, Aug 02, 2010 at 02:22:12PM +0530, Subrata Modak wrote:
> > Hi,
> >
> > The following suspicious rcu_dereference_check() usage is detected
> > during 2.6.35-stable boot on my ppc64/p7 machine:
> >
> > =========================
> > [ INFO: suspicious rcu_dereference_check() usage. ]
> > ---------------------------------------------------
> > kernel/sched.c:616 invoked rcu_dereference_check() without protection!
> > other info that might help us debug this:

> Thank you for locating this one!  This looks like the same issue that
> Ilia Mirkin located.  Please see below for my analysis -- no fix yet,
> as I need confirmation from cgroups experts.  I can easily create a
> patch that suppresses the warning, but I don't yet know whether this is
> the right thing to do.

Ping?  I just hit it on 2.6.36-rc4-mmotm0915.  Just wanted to make sure the
issue hadn't been lost/forgotten.

[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2010-09-16 15:12 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
2010-08-13  7:42     ` Dhaval Giani
2010-08-13  7:42       ` Dhaval Giani
     [not found]     ` <1281682514.5976.2.camel-NRFfyExJdYpgXGGE5LP+UZlqa2bBAFbm0E9HWUfgJXw@public.gmane.org>
2010-08-13  7:42       ` Dhaval Giani
     [not found]   ` <20100809161200.GC3026-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2010-08-13  8:37     ` Subrata Modak
2010-08-13  8:37   ` Subrata Modak
2010-08-13  8:37     ` Subrata Modak
2010-09-16 15:12   ` Valdis.Kletnieks [this message]
2010-09-16 15:12     ` Valdis.Kletnieks
2010-09-16 15:50     ` Peter Zijlstra
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=10430.1284649951@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=a.p.zijlstra@chello.nl \
    --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.