From: Ido Yariv <ido@wizery.com>
To: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Cc: Ido Yariv <ido@wizery.com>
Subject: [PATCH] irq: Fix race condition when stopping the irq thread
Date: Thu, 1 Dec 2011 13:55:08 +0200 [thread overview]
Message-ID: <1322740508-22640-1-git-send-email-ido@wizery.com> (raw)
In irq_wait_for_interrupt(), the should_stop member is verified before
setting the task's state to TASK_INTERRUPTIBLE and calling schedule().
In case kthread_stop sets should_stop and wakes up the process after
should_stop is checked by the irq thread but before the task's state is
changed, the irq thread might never exit:
kthread_stop irq_wait_for_interrupt
------------ ----------------------
...
... while (!kthread_should_stop()) {
kthread->should_stop = 1;
wake_up_process(k);
wait_for_completion(&kthread->exited);
...
set_current_state(TASK_INTERRUPTIBLE);
...
schedule();
}
...
Fix this by checking if the thread should stop after modifying the
task's state.
Signed-off-by: Ido Yariv <ido@wizery.com>
Cc: stable@kernel.org
---
kernel/irq/manage.c | 6 +++++-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index 0e2b179..3194d5e 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -631,7 +631,11 @@ static int irq_wait_for_interrupt(struct irqaction *action)
__set_current_state(TASK_RUNNING);
return 0;
}
- schedule();
+
+ if (!kthread_should_stop())
+ schedule();
+ else
+ __set_current_state(TASK_RUNNING);
}
return -1;
}
--
1.7.7.3
next reply other threads:[~2011-12-01 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 11:55 Ido Yariv [this message]
2011-12-01 21:23 ` [PATCH] irq: Fix race condition when stopping the irq thread Thomas Gleixner
2011-12-02 10:59 ` [tip:irq/urgent] genirq: " tip-bot for Ido Yariv
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=1322740508-22640-1-git-send-email-ido@wizery.com \
--to=ido@wizery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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