From: Tejun Heo <tj@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: workqueue destruction BUG_ON
Date: Tue, 24 Aug 2010 15:15:26 +0200 [thread overview]
Message-ID: <4C73C5EE.2060501@kernel.org> (raw)
In-Reply-To: <1282655865.3695.27.camel@jlt3.sipsolutions.net>
Hello,
On 08/24/2010 03:17 PM, Johannes Berg wrote:
> On Tue, 2010-08-24 at 15:07 +0200, Tejun Heo wrote:
>
>>> [ 500.874185] ------------[ cut here ]------------
>>> [ 500.875212] kernel BUG at kernel/workqueue.c:2849!
>>
>> Are you sure you're running the patched kernel? With the patch
>> applied, the BUG_ON() wouldn't be on line 2849 (on both rc1 and 2).
>
> Yes:
>
> void destroy_workqueue(struct workqueue_struct *wq)
> {
> unsigned int cpu;
>
> wq->flags |= WQ_DYING;
> flush_workqueue(wq);
>
> /*
> * wq list is used to freeze wq, remove from list after
> * flushing is complete in case freeze races us.
> */
> spin_lock(&workqueue_lock);
> list_del(&wq->list);
> spin_unlock(&workqueue_lock);
>
> /* sanity check */
> for_each_cwq_cpu(cpu, wq) {
> struct cpu_workqueue_struct *cwq = get_cwq(cpu, wq);
> int i;
>
> for (i = 0; i < WORK_NR_COLORS; i++)
> BUG_ON(cwq->nr_in_flight[i]);
> 2849: BUG_ON(cwq->nr_active);
> BUG_ON(!list_empty(&cwq->delayed_works));
>
>
> Applying the patch reported some offset, but the kernel is just rc1 +
> wireless stuff.
I see, thanks for verifying. I probably got confused about the line
number. Hmm... weird. I'll prep further debug patch but can you
please tell me what you did to trigger the bug?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-08-24 13:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 8:55 workqueue destruction BUG_ON Johannes Berg
2010-08-24 10:24 ` Tejun Heo
2010-08-24 10:37 ` Johannes Berg
2010-08-24 12:35 ` Tejun Heo
2010-08-24 13:04 ` Johannes Berg
2010-08-24 13:10 ` Johannes Berg
2010-08-24 13:07 ` Tejun Heo
2010-08-24 13:17 ` Johannes Berg
2010-08-24 13:15 ` Tejun Heo [this message]
2010-08-24 13:23 ` Johannes Berg
2010-08-24 14:56 ` Tejun Heo
2010-08-24 15:52 ` Johannes Berg
2010-08-24 15:47 ` Tejun Heo
2010-08-24 15:56 ` Johannes Berg
2010-08-24 13:19 ` Johannes Berg
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=4C73C5EE.2060501@kernel.org \
--to=tj@kernel.org \
--cc=johannes@sipsolutions.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox