From: Thomas Tuttle <ttuttle@chromium.org>
To: lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH] workqueue: lock cwq access in drain_workqueue
Date: Fri, 9 Sep 2011 11:22:22 -0400 [thread overview]
Message-ID: <20110909152222.GA14705@google.com> (raw)
Take cwq->gcwq->lock to avoid racing between drain_workqueue checking
to make sure the workqueues are empty and cwq_dec_nr_in_flight
decrementing and then incrementing nr_active when it activates a
delayed work.
We discovered this when a corner case in one of our drivers resulted in
us trying to destroy a workqueue in which the remaining work would
always requeue itself again in the same workqueue. We would hit this
race condition and trip the BUG_ON on workqueue.c:3080.
Patch is against HEAD as of Fri Sep 9 15:16:09 UTC 2011
(e4e436e0bd480668834fe6849a52c5397b7be4fb).
Signed-off-by: Thomas Tuttle <ttuttle@chromium.org>
---
kernel/workqueue.c | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index 25fb1b0..d610ced 100644
--- a/kernel/workqueue.c
+++ b/kernel/workqueue.c
@@ -2412,8 +2412,14 @@ reflush:
for_each_cwq_cpu(cpu, wq) {
struct cpu_workqueue_struct *cwq = get_cwq(cpu, wq);
+ int cwq_flushed;
- if (!cwq->nr_active && list_empty(&cwq->delayed_works))
+ spin_lock_irq(&cwq->gcwq->lock);
+ cwq_flushed = !cwq->nr_active
+ && list_empty(&cwq->delayed_works);
+ spin_unlock_irq(&cwq->gcwq->lock);
+
+ if (cwq_flushed)
continue;
if (++flush_cnt == 10 ||
--
1.7.3.1
next reply other threads:[~2011-09-09 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 15:22 Thomas Tuttle [this message]
2011-09-09 23:00 ` [PATCH v2] workqueue: lock cwq access in drain_workqueue Thomas Tuttle
2011-09-11 1:35 ` Tejun Heo
2011-09-11 3:26 ` [PATCH v3] " Thomas Tuttle
2011-09-11 3:30 ` Tejun Heo
2011-09-11 3:39 ` Thomas Tuttle
2011-09-11 3:48 ` 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=20110909152222.GA14705@google.com \
--to=ttuttle@chromium.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.