linux-kernel - Re: RCU idle CPU detection is broken in linux-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <505C6B03.7020305@gmail.com>
Date:	Fri, 21 Sep 2012 15:26:27 +0200
From:	Sasha Levin <levinsasha928@...il.com>
To:	paulmck@...ux.vnet.ibm.com
CC:	Michael Wang <wangyun@...ux.vnet.ibm.com>,
	Dave Jones <davej@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: RCU idle CPU detection is broken in linux-next

On 09/21/2012 02:13 PM, Paul E. McKenney wrote:
>> This might be unrelated, but I got the following dump as well when trinity
>> > decided it's time to reboot my guest:
> OK, sounds like we should hold off until you reproduce, then.

I'm not sure what you mean.

There are basically two issues I'm seeing now, which reproduce pretty much every
time:

 1. The "using when idle" warning.
 2. The rcu related hangs during shutdown.

The first one appears early on when I start fuzzing, the other one happens when
shutting down - so both of them are reproducible in the same session.


Thanks,
Sasha
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/