lkml.org 
[lkml]   [2011]   [Aug]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [kernel.org users] [KORG] Panics on master backend
From
Date
On Thu, 2011-08-25 at 15:54 +0200, Oleg Nesterov wrote:
> > Isn't us holding ->pi_lock sufficient to stabilize task_cpu()? If its a
> > running task the initial ->state check would have failed,
>
> Of course it is not TASK_RUNNING, but it can be running or not.
>
> > and thus its a
> > proper wakeup when we get here and thus ->pi_lock is serializing things.
>
> I am not sure. If ->on_rq is true, we need rq->lock. Say, pull_task() can
> change its cpu.

If its !TASK_RUNNING but ->on_rq is true, it must be current, and
pull_task() will never move current around.




\
 
 \ /
  Last update: 2011-08-29 15:11    [W:0.078 / U:0.200 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site