From: Peter Zijlstra <peterz@infradead.org>
To: Rajan Aggarwal <rajan.aggarwal85@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] fs-writeback: Using spin_lock to check for work_list empty
Date: Thu, 01 Sep 2011 13:56:54 +0200 [thread overview]
Message-ID: <1314878214.11566.8.camel@twins> (raw)
In-Reply-To: <1314767509-17862-1-git-send-email-rajan.aggarwal85@gmail.com>
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
prev parent reply other threads:[~2011-09-01 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 5:11 [PATCH 1/1] fs-writeback: Using spin_lock to check for work_list empty Rajan Aggarwal
2011-08-31 6:46 ` Rajan Aggarwal
2011-08-31 6:51 ` Rajan Aggarwal
2011-08-31 21:27 ` Andrew Morton
2011-09-01 7:54 ` KAMEZAWA Hiroyuki
2011-09-01 11:56 ` Peter Zijlstra [this message]
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=1314878214.11566.8.camel@twins \
--to=peterz@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rajan.aggarwal85@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).