#4: (kbd_event_lock){....}, at: [<ffffffff826f2413>] spin_lock include/linux/spinlock.h:316 [inline]
#4: (kbd_event_lock){....}, at: [<ffffffff826f2413>] kbd_event+0x2e3/0x4870 drivers/tty/vt/keyboard.c:1458
#5: (tasklist_lock){.?.?}, at: [<ffffffff81540122>] debug_show_all_locks+0xd2/0x410 kernel/locking/lockdep.c:4552
=============================================
BUG: workqueue lockup - pool cpus=1 node=0 flags=0x0 nice=0 stuck for 62s!
Showing busy workqueues and worker pools:
workqueue events: flags=0x0
pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=3/256
in-flight: 3277:console_callback, 24:linkwatch_event linkwatch_event
pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=2/256
pending: vmstat_shepherd, cache_reap
workqueue events_long: flags=0x0
pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256
pending: gc_worker
workqueue events_power_efficient: flags=0x80
pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256
pending: neigh_periodic_work
workqueue mm_percpu_wq: flags=0x8
pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256
pending: vmstat_update
workqueue writeback: flags=0x4e
pwq 4: cpus=0-1 flags=0x4 nice=0 active=1/256
in-flight: 4460:wb_workfn
workqueue kblockd: flags=0x18
pwq 1: cpus=0 node=0 flags=0x0 nice=-20 active=1/256
pending: blk_timeout_work
pool 2: cpus=1 node=0 flags=0x0 nice=0 hung=0s workers=4 idle: 3274 31368
pool 4: cpus=0-1 flags=0x4 nice=0 hung=0s workers=12 idle: 3599 57 5 22496 10223 3304 3298 21 3416 4468 22502
=============================
WARNING: suspicious RCU usage
4.13.0+ #68 Not tainted
-----------------------------
./include/linux/kvm_host.h:481 suspicious rcu_dereference_check() usage!
other info that might help us debug this:
rcu_scheduler_active = 2, debug_locks = 1
no locks held by syz-executor1/1668.
stack backtrace:
CPU: 0 PID: 1668 Comm: syz-executor1 Not tainted 4.13.0+ #68
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:16 [inline]
dump_stack+0x194/0x257 lib/dump_stack.c:52
lockdep_rcu_suspicious+0x123/0x170 kernel/locking/lockdep.c:4673
kvm_get_bus include/linux/kvm_host.h:479 [inline]
kvm_create_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:678 [inline]
kvm_dev_ioctl_create_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:3152 [inline]
kvm_dev_ioctl+0x877/0x1840 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3203
vfs_ioctl fs/ioctl.c:45 [inline]
do_vfs_ioctl+0x1b1/0x1530 fs/ioctl.c:685
SYSC_ioctl fs/ioctl.c:700 [inline]
SyS_ioctl+0x8f/0xc0 fs/ioctl.c:691
entry_SYSCALL_64_fastpath+0x1f/0xbe
RIP: 0033:0x451e59
RSP: 002b:00007f39f6d5ec08 EFLAGS: 00000216 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000007180b0 RCX: 0000000000451e59
RDX: 0000000000000000 RSI: 000000000000ae01 RDI: 0000000000000017
RBP: 0000000000000082 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000216 R12: 0000000000000000
R13: 0000000000a6f7ef R14: 00007f39f6d5f9c0 R15: 000000000000001a
=============================
WARNING: suspicious RCU usage
4.13.0+ #68 Not tainted
-----------------------------
./include/linux/kvm_host.h:575 suspicious rcu_dereference_check() usage!
other info that might help us debug this:
rcu_scheduler_active = 2, debug_locks = 1
no locks held by syz-executor1/1668.
stack backtrace:
CPU: 0 PID: 1668 Comm: syz-executor1 Not tainted 4.13.0+ #68
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:16 [inline]
dump_stack+0x194/0x257 lib/dump_stack.c:52
lockdep_rcu_suspicious+0x123/0x170 kernel/locking/lockdep.c:4673
__kvm_memslots include/linux/kvm_host.h:573 [inline]
kvm_create_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:680 [inline]
kvm_dev_ioctl_create_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:3152 [inline]
kvm_dev_ioctl+0xd21/0x1840 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3203
vfs_ioctl fs/ioctl.c:45 [inline]
do_vfs_ioctl+0x1b1/0x1530 fs/ioctl.c:685
SYSC_ioctl fs/ioctl.c:700 [inline]
SyS_ioctl+0x8f/0xc0 fs/ioctl.c:691
entry_SYSCALL_64_fastpath+0x1f/0xbe
RIP: 0033:0x451e59
RSP: 002b:00007f39f6d5ec08 EFLAGS: 00000216 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000007180b0 RCX: 0000000000451e59
RDX: 0000000000000000 RSI: 000000000000ae01 RDI: 0000000000000017
RBP: 0000000000000082 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000216 R12: 0000000000000000
R13: 0000000000a6f7ef R14: 00007f39f6d5f9c0 R15: 000000000000001a
device syz4 left promiscuous mode
yam0: port 1(syz4) entered disabled state
netlink: 11 bytes leftover after parsing attributes in process `syz-executor5'.
netlink: 11 bytes leftover after parsing attributes in process `syz-executor5'.
device gre0 entered promiscuous mode
skbuff: bad partial csum: csum=98/65532 len=264
skbuff: bad partial csum: csum=98/65532 len=264
device lo entered promiscuous mode
sctp: [Deprecated]: syz-executor4 (pid 2193) Use of int in maxseg socket option.
Use struct sctp_assoc_value instead
netlink: 1 bytes leftover after parsing attributes in process `syz-executor5'.
sg_write: data in/out 3171656/6 bytes for SCSI command 0x0-- guessing data in;
program syz-executor6 not setting count and/or reply_len properly
sg_write: data in/out 3171656/6 bytes for SCSI command 0x0-- guessing data in;
program syz-executor6 not setting count and/or reply_len properly
netlink: 1 bytes leftover after parsing attributes in process `syz-executor7'.
netlink: 1 bytes leftover after parsing attributes in process `syz-executor7'.
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
SELinux: unrecognized netlink message: protocol=9 nlmsg_type=0 sclass=netlink_audit_socket pig=2454 comm=syz-executor6
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pig=2440 comm=syz-executor7
SELinux: unrecognized netlink message: protocol=9 nlmsg_type=0 sclass=netlink_audit_socket pig=2454 comm=syz-executor6
netlink: 12 bytes leftover after parsing attributes in process `syz-executor0'.
netlink: 12 bytes leftover after parsing attributes in process `syz-executor0'.