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]

Date:	Sun, 23 Sep 2012 07:39:39 +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>,
	fweisbec@...il.com
Subject: Re: RCU idle CPU detection is broken in linux-next

On 09/23/2012 02:21 AM, Paul E. McKenney wrote:
> On Sat, Sep 22, 2012 at 02:27:35PM -0700, Paul E. McKenney wrote:
>> On Sat, Sep 22, 2012 at 07:50:29PM +0200, Sasha Levin wrote:
>>> On 09/22/2012 05:56 PM, Paul E. McKenney wrote:
>>>> And now the prime suspect is the new CONFIG_RCU_USER_QS=y.  Do these
>>>> warnings ever show up with CONFIG_RCU_USER_QS=n?
>>>
>>> It seems that disabling that does make the warnings go away.
>>>
>>> I'll keep the tests running in case it just reduces the chances or something
>>> like that.
>>
>> Thank you for testing this!
>>
>> And of course the reason that I didn't see these problems is that I
>> failed to update my tests to enable CONFIG_RCU_USER_QS.  :-/
> 
> Also the fact that I run 32-bit guests on x86.  Sigh!
> 
> I take it that you are running 64-bit guests?

Yes, that's correct.


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/