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: <CAFTL4hyj43L1b_7B+BjSbdGAE4RNYqFBz01G+ifwKu=0k9v+2w@mail.gmail.com>
Date:	Wed, 26 Sep 2012 16:58:01 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Sasha Levin <levinsasha928@...il.com>
Cc:	paulmck@...ux.vnet.ibm.com,
	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

2012/9/25 Sasha Levin <levinsasha928@...il.com>:
> On 09/25/2012 02:06 PM, Frederic Weisbecker wrote:
>> Sasha, sorry to burden you with more testing request.
>> Could you please try out this new branch? It includes some fixes after Wu Fenguang and
>> Dan Carpenter reports (not related to your warnings though) and a patch on the top
>> of the pile to ensure I diagnosed well the problem, which return immediately from
>> rcu_user_*() APIs if we are in an interrupt.
>>
>> This way we'll have a clearer view. I also would like to know if there are other
>> problems with the rcu user mode.
>>
>> Thanks!
>
> Alrighty, I don't see any warnings anymore.
>
> I'll keep everything running just in case.

Cool! I'm pushing the fix tree to Paul then.

Thanks a lot for your testing!
--
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/