From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: kernel BUG at kernel/workqueue
Date: Thu, 26 May 2011 00:45:10 +0700 [thread overview]
Message-ID: <BANLkTiky4+77=o1D-n2Y5iy79y8PENEUdA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimD9ihEuzTwMaTOroPiorvYx8mYcg@mail.gmail.com>
Hi...
On Wed, May 25, 2011 at 16:32, sri <bskmohan@gmail.com> wrote:
> kernel BUG at kernel/workqueue.c:113!
from http://lxr.linux.no/#linux+v2.6.18/kernel/workqueue.c, lines around 113:
int fastcall queue_work(struct workqueue_struct *wq, struct work_struct *work)
107{
108 int ret = 0, cpu = get_cpu();
109
110 if (!test_and_set_bit(0, &work->pending)) {
111 if (unlikely(is_single_threaded(wq)))
112 cpu = singlethread_cpu;
113 BUG_ON(!list_empty(&work->entry));
114 __queue_work(per_cpu_ptr(wq->cpu_wq, cpu), work);
115 ret = 1;
116 }
117 put_cpu();
118 return ret;
119}
So, if I interpret it correctly, that BUG_ON line means that if
work->entry is not empty or null, then it is a bug.
Not sure what causes that, but it could be simply due to failure of
"work" initialization (as work_struct) somewhere...
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next prev parent reply other threads:[~2011-05-25 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 9:32 kernel BUG at kernel/workqueue sri
2011-05-25 17:45 ` Mulyadi Santosa [this message]
2011-05-26 12:33 ` sri
2011-05-27 2:13 ` Mulyadi Santosa
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='BANLkTiky4+77=o1D-n2Y5iy79y8PENEUdA@mail.gmail.com' \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).