| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20100203122755.0fd4fb7e@marrow.netinsight.se>
Date: Wed, 3 Feb 2010 12:27:55 +0100
From: Simon Kagstrom <simon.kagstrom@...insight.net>
To: linux-kernel@...r.kernel.org, laijs@...fujitsu.com
Cc: oleg@...hat.com, rusty@...tcorp.com.au, tj@...nel.org,
akpm@...ux-foundation.org, mingo@...e.hu
Subject: [PATCH] core: workqueue: BUG_ON on workqueue recursion
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@...insight.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists