linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: linux-kernel@vger.kernel.org, laijs@cn.fujitsu.com
Cc: oleg@redhat.com, rusty@rustcorp.com.au, tj@kernel.org,
	akpm@linux-foundation.org, mingo@elte.hu
Subject: [PATCH] core: workqueue: BUG_ON on workqueue recursion
Date: Wed, 3 Feb 2010 12:27:55 +0100	[thread overview]
Message-ID: <20100203122755.0fd4fb7e@marrow.netinsight.se> (raw)

When the workqueue is flushed from workqueue context (recursively), the
system enters a strange state where things at random (dependent on the
global workqueue) start misbehaving. For example, for us the console and
logins locks up while the web server continues running.

Since the system becomes unstable, change this to a BUG_ON instead.

Signed-off-by: Simon Kagstrom <simon.kagstrom@netinsight.net>
---
 kernel/workqueue.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index dee4865..e617d29 100644
--- a/kernel/workqueue.c
+++ b/kernel/workqueue.c
@@ -482,7 +482,7 @@ static int flush_cpu_workqueue(struct cpu_workqueue_struct *cwq)
 	int active = 0;
 	struct wq_barrier barr;
 
-	WARN_ON(cwq->thread == current);
+	BUG_ON(cwq->thread == current);
 
 	spin_lock_irq(&cwq->lock);
 	if (!list_empty(&cwq->worklist) || cwq->current_work != NULL) {
-- 
1.6.0.4


             reply	other threads:[~2010-02-03 11:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 11:27 Simon Kagstrom [this message]
2010-02-03 19:43 ` [PATCH] core: workqueue: BUG_ON on workqueue recursion Oleg Nesterov
2010-02-04  2:12   ` Tejun Heo
2010-02-04  8:02     ` [PATCH v2] core: workqueue: return " Simon Kagstrom
2010-02-04 10:52       ` Oleg Nesterov
2010-02-12  8:47       ` Tejun Heo
2010-02-04  2:00 ` [PATCH] core: workqueue: BUG_ON " Lai Jiangshan

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=20100203122755.0fd4fb7e@marrow.netinsight.se \
    --to=simon.kagstrom@netinsight.net \
    --cc=akpm@linux-foundation.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=tj@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 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).