From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: subrata@linux.vnet.ibm.com
Cc: Linuxppc-dev <Linuxppc-dev@ozlabs.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Suspicious rcu_dereference_check() usage detected during 2.6.34-rc6 boot on PPC64/p5 processor
Date: Fri, 7 May 2010 16:17:49 +0200 [thread overview]
Message-ID: <201005071617.49253.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <1273130279.4898.5.camel@subratamodak.linux.ibm.com>
On czwartek, 6 maja 2010 o 09:17:59 Subrata Modak wrote:
> Hi,
>
> The following messages were logged into /var/log/messages when i booted
> 2.6.34-rc6 kernel (built with attached CONFIG file contents ) on my p5 box:
>
I created a Bugzilla entry at
https://bugzilla.kernel.org/show_bug.cgi?id=15936
for your bug report, please add your address to the CC list in there, thanks!
--
Maciej Rutecki
http://www.maciek.unixy.pl
next prev parent reply other threads:[~2010-05-07 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 7:17 Suspicious rcu_dereference_check() usage detected during 2.6.34-rc6 boot on PPC64/p5 processor Subrata Modak
2010-05-07 14:17 ` Maciej Rutecki [this message]
2010-05-07 15:54 ` Paul E. McKenney
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=201005071617.49253.maciej.rutecki@gmail.com \
--to=maciej.rutecki@gmail.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).