linux-kernel - Re: race condition in schedule_on_each

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>] [day] [month] [year] [list]

Message-ID: <51B315CD.9010908@kylinos.com.cn>
Date:	Sat, 08 Jun 2013 19:30:21 +0800
From:	"weiqi@...inos.com.cn" <weiqi@...inos.com.cn>
To:	Tejun Heo <tj@...nel.org>
CC:	"weiqi@...inos.com.cn" <weiqi@...inos.com.cn>,
	torvalds <torvalds@...ux-foundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: race condition in schedule_on_each_cpu()

Hello Tejun Heo,

I've backported the  schedule_on_each_cpu()  "direct excution" patch on 
3.0.30-rt50,
and  It  fixed my problem.

attachment is the effective patch.

However, I do not understand why  machine1 can expose problem,  but 
machine2 not.

I guess, because it's  rt-kernel's  preempt level related, so , is this 
difference due to cpu performance?

How do you think about this ?

Thank you~

View attachment "direct_execution.patch" of type "text/plain" (1171 bytes)