From: Lin Ming <ming.m.lin@intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Maciej Rutecki <maciej.rutecki@gmail.com>,
Florian Mickler <florian@mickler.org>,
Miles Lane <miles.lane@gmail.com>
Subject: Re: [Bug #37222] 3.0.0-rc1-git3 -- kernel/sched.c:619 invoked rcu_dereference_check() without protection!
Date: Mon, 13 Jun 2011 10:00:06 +0800 [thread overview]
Message-ID: <1307930406.4011.3.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <BANLkTikjZ7O6SFmD2e-YnMztGHoGZL69qg@mail.gmail.com>
> From: Rafael J. Wysocki <rjw@sisk.pl>
> Date: Mon, Jun 13, 2011 at 4:30 AM
> Subject: [Bug #37222] 3.0.0-rc1-git3 -- kernel/sched.c:619 invoked
> rcu_dereference_check() without protection!
> To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
> Cc: Kernel Testers List <kernel-testers@vger.kernel.org>, Maciej
> Rutecki <maciej.rutecki@gmail.com>, Florian Mickler
> <florian@mickler.org>, Miles Lane <miles.lane@gmail.com>
>
>
> This message has been generated automatically as a part of a summary report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.39. Please verify if it still should be listed and let the
> tracking team
> know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=37222
> Subject : 3.0.0-rc1-git3 -- kernel/sched.c:619 invoked
> rcu_dereference_check() without protection!
> Submitter : Miles Lane <miles.lane@gmail.com>
> Date : 2011-06-04 3:22 (9 days old)
> Message-ID : <BANLkTikHS7TuFhm3cfJ+Y=erWDaAwuE_TA@mail.gmail.com>
> References : http://marc.info/?l=linux-kernel&m=130715775803343&w=2
>
This was fixed already.
http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=commit;h=6c6c54e180
commit 6c6c54e1807faf116724451ef2bd14993780470a
Author: Peter Zijlstra <peterz@infradead.org>
Date: Fri Jun 3 17:37:07 2011 +0200
sched: Fix/clarify set_task_cpu() locking rules
Thanks,
Lin Ming
next prev parent reply other threads:[~2011-06-13 1:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 20:23 3.0-rc2: Reported regressions from 2.6.39 Rafael J. Wysocki
2011-06-12 20:23 ` [Bug #36302] SandyBridge can't do s2disk with linux 3.0-rc1 Rafael J. Wysocki
2011-06-12 20:30 ` [Bug #36452] Artifacts with 3.0-rc1 on SandyBridge Rafael J. Wysocki
2011-06-15 18:43 ` Jesse Barnes
2011-06-15 18:59 ` Alexander Zhaunerchyk
2011-06-15 21:15 ` Florian Mickler
2011-06-12 20:30 ` [Bug #37222] 3.0.0-rc1-git3 -- kernel/sched.c:619 invoked rcu_dereference_check() without protection! Rafael J. Wysocki
[not found] ` <BANLkTikjZ7O6SFmD2e-YnMztGHoGZL69qg@mail.gmail.com>
2011-06-13 2:00 ` Lin Ming [this message]
2011-06-13 17:26 ` Rafael J. Wysocki
2011-06-12 20:30 ` [Bug #36972] 3.0-rc1: DMAR errors from iwlagn Rafael J. Wysocki
2011-06-13 20:09 ` Jeremy Fitzhardinge
2011-06-13 21:21 ` Rafael J. Wysocki
2011-06-12 20:30 ` [Bug #36982] 3.0-rc1 problem with usb, cdrom Rafael J. Wysocki
2011-06-12 20:30 ` [Bug #37232] [3.0-rc1][NMI/DMAR][iwlagn] errors - PCI system error (SERR) for reason a1 on CPU 0 Rafael J. Wysocki
2011-06-19 2:34 ` Shawn Starr
2011-06-19 13:46 ` Rafael J. Wysocki
2011-06-12 20:30 ` [Bug #37242] lockdep deadlock warning in shutdown Rafael J. Wysocki
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=1307930406.4011.3.camel@minggr.sh.intel.com \
--to=ming.m.lin@intel.com \
--cc=florian@mickler.org \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=miles.lane@gmail.com \
--cc=rjw@sisk.pl \
/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