From: Eric Biggers <ebiggers3@gmail.com>
To: syzbot
<bot+e38be687a2450270a3b593bacb6b5795a7a74edb@syzkaller.appspotmail.com>
Cc: dvyukov@google.com, gregkh@linuxfoundation.org,
kstewart@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, penguin-kernel@I-love.SAKURA.ne.jp,
pombredanne@nexb.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de
Subject: Re: BUG: workqueue lockup (2)
Date: Sat, 12 May 2018 14:52:22 -0700 [thread overview]
Message-ID: <20180512215222.GC817@sol.localdomain> (raw)
In-Reply-To: <001a113f711a528a3f0560b08e76@google.com>
On Tue, Dec 19, 2017 at 04:25:01AM -0800, syzbot wrote:
> syzkaller has found reproducer for the following crash on
> f3b5ad89de16f5d42e8ad36fbdf85f705c1ae051
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
> C reproducer is attached
> syzkaller reproducer is attached. See https://goo.gl/kgGztJ
> for information about syzkaller reproducers
>
>
> BUG: workqueue lockup - pool cpus=1 node=0 flags=0x0 nice=0 stuck for 37s!
> BUG: workqueue lockup - pool cpus=1 node=0 flags=0x0 nice=-20 stuck for 32s!
> Showing busy workqueues and worker pools:
> workqueue events: flags=0x0
> pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/256
> pending: cache_reap
> workqueue events_power_efficient: flags=0x80
> pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=2/256
> pending: neigh_periodic_work, do_cache_clean
> workqueue mm_percpu_wq: flags=0x8
> pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/256
> pending: vmstat_update
> workqueue kblockd: flags=0x18
> pwq 3: cpus=1 node=0 flags=0x0 nice=-20 active=1/256
> pending: blk_timeout_work
>
The bug that this reproducer reproduces was fixed a while ago by commit
966031f340185e, so I'm marking this bug report fixed by it:
#syz fix: n_tty: fix EXTPROC vs ICANON interaction with TIOCINQ (aka FIONREAD)
Note that the error message was not always "BUG: workqueue lockup"; it was also
sometimes like "watchdog: BUG: soft lockup - CPU#5 stuck for 22s!".
syzbot still is hitting the "BUG: workqueue lockup" error sometimes, but it must
be for other reasons. None has a reproducer currently.
- Eric
next prev parent reply other threads:[~2018-05-12 21:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 14:31 BUG: workqueue lockup (2) syzbot
2017-12-03 14:36 ` Dmitry Vyukov
2017-12-03 14:36 ` Dmitry Vyukov
2017-12-03 14:48 ` Thomas Gleixner
2017-12-03 14:48 ` Thomas Gleixner
2017-12-04 11:08 ` Tetsuo Handa
2017-12-04 11:08 ` Tetsuo Handa
2017-12-19 12:25 ` syzbot
2017-12-19 14:27 ` Tetsuo Handa
2017-12-19 14:27 ` Tetsuo Handa
2017-12-19 14:40 ` Dmitry Vyukov
2017-12-19 14:40 ` Dmitry Vyukov
2017-12-19 16:37 ` Dmitry Vyukov
2017-12-19 16:37 ` Dmitry Vyukov
2017-12-20 10:55 ` Tetsuo Handa
2017-12-20 10:55 ` Tetsuo Handa
2017-12-21 10:19 ` Dmitry Vyukov
2017-12-21 10:19 ` Dmitry Vyukov
2017-12-21 10:22 ` Dmitry Vyukov
2017-12-21 10:22 ` Dmitry Vyukov
2017-12-21 11:04 ` Dmitry Vyukov
2017-12-21 11:04 ` Dmitry Vyukov
2017-12-21 13:07 ` Tetsuo Handa
2017-12-21 13:07 ` Tetsuo Handa
2017-12-28 13:43 ` Dmitry Vyukov
2017-12-28 13:43 ` Dmitry Vyukov
2018-05-12 21:52 ` Eric Biggers [this message]
2018-05-13 2:06 ` Tetsuo Handa
2018-05-13 3:32 ` Eric Biggers
2018-05-13 14:29 ` Tetsuo Handa
2018-05-13 14:35 ` Dmitry Vyukov
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=20180512215222.GC817@sol.localdomain \
--to=ebiggers3@gmail.com \
--cc=bot+e38be687a2450270a3b593bacb6b5795a7a74edb@syzkaller.appspotmail.com \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=pombredanne@nexb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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.