BUG: workqueue lockup - pool cpus=1 node=0 flags=0x0 nice=0 stuck for 40s!

628 views
Skip to first unread message

syzbot

unread,
Sep 1, 2017, 2:59:04 PM9/1/17
to syzkaller-upst...@googlegroups.com
Hello,

syzkaller hit the following crash on
e8b684315214053f29f7f78643aefd19da342976
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.


CC: []

TCP: request_sock_TCP: Possible SYN flooding on port 20028. Sending
cookies. Check SNMP counters.
BUG: workqueue lockup - pool cpus=1 node=0 flags=0x0 nice=0 stuck for 40s!
Showing busy workqueues and worker pools:
workqueue events: flags=0x0
pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/256
in-flight: 800:key_garbage_collector
pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=2/256
pending: e1000_watchdog, vmstat_shepherd
workqueue mm_percpu_wq: flags=0x8
pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=2/256
pending: lru_add_drain_per_cpu BAR(5819), vmstat_update
pool 2: cpus=1 node=0 flags=0x0 nice=0 hung=40s workers=4 idle: 1263 3928 18


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.

syzbot will keep track of this bug report.
Once a fix for this bug is committed, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
To upstream this report, please reply with:
#syz upstream
config.txt
raw.log

Dmitry Vyukov

unread,
Nov 3, 2017, 8:58:27 AM11/3/17
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
This bug title was superseded by "BUG: workqueue lockup" title

#syz invalid

On Fri, Sep 1, 2017 at 9:59 PM, syzbot
<bot+097de6f841e96a51ee...@syzkaller.appspotmail.com>
wrote:
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To post to this group, send email to
> syzkaller-upst...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/001a11c14e229fc7b10558255a94%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages