From: "weiqi@kylinos.com.cn" <weiqi@kylinos.com.cn>
To: Tejun Heo <tj@kernel.org>
Cc: "weiqi@kylinos.com.cn" <weiqi@kylinos.com.cn>,
torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: race condition in schedule_on_each_cpu()
Date: Fri, 07 Jun 2013 10:24:50 +0800 [thread overview]
Message-ID: <51B14472.60904@kylinos.com.cn> (raw)
In-Reply-To: <51B138AA.4070707@kylinos.com.cn>
In the previous message,You mentioned:
>> by the way, I'm wondering about what's the race condition before
which doesn't exist now
> Before the commit you originally quoted, the calling thread could be
preempted and migrated to another CPU before get_online_cpus() thus
ending up executing the function twice on the new cpu but skipping the
old one.
does this situation will happen in "Full preemption" config, on 3.0.30-rt50?
于 2013年06月07日 09:34, weiqi@kylinos.com.cn 写道:
> it's preemption mode related ,
>
> on the 3.0.30-rt50, only config kernel with highest preemption
> level (Fully Preemptible Kernel (RT)) in cpu preemption model
> will cause problem
>
> and even i use the "Preemptible Kernel" or "Preemptible Kernel
> (Low-Latency Desktop)" the problem would not happen..
>
>
> > I looked through the logs but the only worker depletion related
> patches which pop up are around CPU hotplugs, so I don't think they
> apply here. If the problem is relatively easy to reproduce && you
> can't move onto a newer kernel, I'm afraid bisection probably is the
> best option. Thanks!
>
next prev parent reply other threads:[~2013-06-07 2:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_0777D84B54B4163A3B85255A@qq.com>
2013-06-06 21:23 ` race condition in schedule_on_each_cpu() Tejun Heo
2013-06-07 1:34 ` weiqi
2013-06-07 2:24 ` weiqi [this message]
2013-06-07 23:22 ` Tejun Heo
[not found] ` <51B27744.6090507@kylinos.com.cn>
2013-06-08 11:30 ` weiqi
[not found] <51A7FFE8.6060204@kylinos.com.cn>
[not found] ` <20130531023246.GD30479@mtj.dyndns.org>
[not found] ` <51A821F3.1000605@kylinos.com.cn>
2013-05-31 5:03 ` Tejun Heo
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=51B14472.60904@kylinos.com.cn \
--to=weiqi@kylinos.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
/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