Re: [PATCH 1/1] fs-writeback: Using spin_lock to check forwork_list empty

[Peter Zijlstra]

On Wed, 2011-08-31 at 10:41 +0530, Rajan Aggarwal wrote:
> 
> If the list is not empty, and if an interrupt happens before we
> set the current->state to TASK_RUNNING then we could be stuck in
> a schedule() due to kernel preemption. 

No, look at PREEMPT_ACTIVE use in kernel/sched.c
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/