[v6.1] INFO: task hung in __lru_add_drain_all

2 views
Skip to first unread message

syzbot

unread,
May 17, 2024, 4:43:36 PMMay 17
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 4078fa637fcd Linux 6.1.91
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=139b60dc980000
kernel config: https://syzkaller.appspot.com/x/.config?x=715ba80acfd3def4
dashboard link: https://syzkaller.appspot.com/bug?extid=96373a7d83fc81843a24
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2443dfe91c62/disk-4078fa63.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/12dbc2af3348/vmlinux-4078fa63.xz
kernel image: https://storage.googleapis.com/syzbot-assets/da3589238e32/bzImage-4078fa63.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+96373a...@syzkaller.appspotmail.com

INFO: task syz-executor.2:3570 blocked for more than 143 seconds.
Not tainted 6.1.91-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D stack:21016 pid:3570 ppid:1 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_timeout+0xac/0x300 kernel/time/timer.c:1941
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x350/0x610 kernel/sched/completion.c:138
__flush_work+0x95b/0xad0 kernel/workqueue.c:3076
__lru_add_drain_all+0x669/0x7d0 mm/swap.c:918
invalidate_bdev+0x8f/0xb0 block/bdev.c:86
ext4_put_super+0x96d/0x10e0 fs/ext4/super.c:1281
generic_shutdown_super+0x130/0x340 fs/super.c:501
kill_block_super+0x7a/0xe0 fs/super.c:1459
deactivate_locked_super+0xa0/0x110 fs/super.c:332
cleanup_mnt+0x490/0x520 fs/namespace.c:1186
task_work_run+0x246/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xde/0x100 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:303
do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7efe33a7e217
RSP: 002b:00007ffc9a8842a8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007efe33a7e217
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffc9a884360
RBP: 00007ffc9a884360 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffc9a885420
R13: 00007efe33ac8336 R14: 000000000004c68c R15: 0000000000000003
</TASK>
INFO: task kworker/u4:5:3596 blocked for more than 143 seconds.
Not tainted 6.1.91-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:5 state:D stack:22816 pid:3596 ppid:2 flags:0x00004000
Workqueue: events_unbound fsnotify_mark_destroy_workfn
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_timeout+0xac/0x300 kernel/time/timer.c:1941
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x350/0x610 kernel/sched/completion.c:138
__synchronize_srcu+0x2b7/0x360 kernel/rcu/srcutree.c:1243
fsnotify_mark_destroy_workfn+0x142/0x340 fs/notify/mark.c:898
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
INFO: task kworker/u4:6:3660 blocked for more than 144 seconds.
Not tainted 6.1.91-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:6 state:D stack:20544 pid:3660 ppid:2 flags:0x00004000
Workqueue: events_unbound fsnotify_connector_destroy_workfn
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_timeout+0xac/0x300 kernel/time/timer.c:1941
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x350/0x610 kernel/sched/completion.c:138
__synchronize_srcu+0x2b7/0x360 kernel/rcu/srcutree.c:1243
fsnotify_connector_destroy_workfn+0x40/0xa0 fs/notify/mark.c:208
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
INFO: task syz-executor.3:8847 blocked for more than 144 seconds.
Not tainted 6.1.91-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3 state:D stack:27112 pid:8847 ppid:5814 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_timeout+0xac/0x300 kernel/time/timer.c:1941
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x350/0x610 kernel/sched/completion.c:138
__synchronize_srcu+0x2b7/0x360 kernel/rcu/srcutree.c:1243
kvm_swap_active_memslots+0x2ed/0x3d0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1593
kvm_activate_memslot arch/x86/kvm/../../../virt/kvm/kvm_main.c:1715 [inline]
kvm_create_memslot arch/x86/kvm/../../../virt/kvm/kvm_main.c:1781 [inline]
kvm_set_memslot+0x5d8/0x1160 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1893
__kvm_set_memory_region+0x80b/0x9d0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2035
kvm_set_memory_region arch/x86/kvm/../../../virt/kvm/kvm_main.c:2048 [inline]
kvm_vm_ioctl_set_memory_region+0x6d/0xa0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2060
kvm_vm_ioctl+0x922/0xb60 arch/x86/kvm/../../../virt/kvm/kvm_main.c:4741
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f1787e7cee9
RSP: 002b:00007f1788caf0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f1787fabf80 RCX: 00007f1787e7cee9
RDX: 0000000020000180 RSI: 000000004020ae46 RDI: 0000000000000004
RBP: 00007f1787ec949e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f1787fabf80 R15: 00007ffca0d44898
</TASK>
INFO: task syz-executor.1:8858 blocked for more than 145 seconds.
Not tainted 6.1.91-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack:25832 pid:8858 ppid:3946 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_timeout+0xac/0x300 kernel/time/timer.c:1941
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x350/0x610 kernel/sched/completion.c:138
__flush_work+0x95b/0xad0 kernel/workqueue.c:3076
flush_work kernel/workqueue.c:3097 [inline]
flush_delayed_work+0x14b/0x1a0 kernel/workqueue.c:3221
fsnotify_destroy_group+0x210/0x330 fs/notify/group.c:76
inotify_release+0x41/0x70 fs/notify/inotify/inotify_user.c:309
__fput+0x3b7/0x890 fs/file_table.c:320
task_work_run+0x246/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xde/0x100 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:303
do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f660027bdda
RSP: 002b:00007fff91c6fb30 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000004 RCX: 00007f660027bdda
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 00007fff91c6fc08 R08: 00007f6600200000 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000000293 R12: 000000000004df7a
R13: 00007f66003abf8c R14: 00007f66003abf80 R15: 0000000000000032
</TASK>
INFO: task syz-executor.0:8874 blocked for more than 146 seconds.
Not tainted 6.1.91-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:25832 pid:8874 ppid:5685 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_timeout+0xac/0x300 kernel/time/timer.c:1941
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x350/0x610 kernel/sched/completion.c:138
__synchronize_srcu+0x2b7/0x360 kernel/rcu/srcutree.c:1243
mmu_notifier_unregister+0x2be/0x3b0 mm/mmu_notifier.c:854
kvm_destroy_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:1322 [inline]
kvm_put_kvm+0xca3/0x18a0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1370
kvm_vcpu_release+0x53/0x60 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3856
__fput+0x3b7/0x890 fs/file_table.c:320
task_work_run+0x246/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xde/0x100 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:303
do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f6579a7bdda
RSP: 002b:00007ffe55c25cc0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000007 RCX: 00007f6579a7bdda
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000006
RBP: 00007ffe55c25d98 R08: 00007f6579a00000 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000000293 R12: 000000000004eea0
R13: 00007f6579babf8c R14: 00007f6579babf80 R15: 0000000000000032
</TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8d12ae50 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8d12b650 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
#0: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6494
2 locks held by kworker/u4:2/33:
2 locks held by getty/3310:
#0: ffff88801427f098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc900031262f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2188
2 locks held by syz-executor.2/3570:
#0: ffff888055ce20e0 (&type->s_umount_key#31){++++}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:362
#1: ffffffff8d1d1f48 (lock#3){+.+.}-{3:3}, at: __lru_add_drain_all+0x66/0x7d0 mm/swap.c:873
2 locks held by kworker/u4:5/3596:
#0: ffff888012479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc9000437fd20 ((reaper_work).work){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
6 locks held by kworker/0:5/3620:
2 locks held by kworker/u4:6/3660:
#0: ffff888012479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90004627d20 (connector_reaper_work){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
6 locks held by kworker/0:14/4324:
2 locks held by syz-executor.4/8826:
1 lock held by syz-executor.3/8847:
#0: ffffc9000337b0a8 (&kvm->slots_lock){+.+.}-{3:3}, at: kvm_set_memory_region arch/x86/kvm/../../../virt/kvm/kvm_main.c:2047 [inline]
#0: ffffc9000337b0a8 (&kvm->slots_lock){+.+.}-{3:3}, at: kvm_vm_ioctl_set_memory_region+0x62/0xa0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2060
1 lock held by syz-executor.3/8921:
#0: ffffc900037c10a8 (&kvm->slots_lock){+.+.}-{3:3}, at: kvm_set_memory_region arch/x86/kvm/../../../virt/kvm/kvm_main.c:2047 [inline]
#0: ffffc900037c10a8 (&kvm->slots_lock){+.+.}-{3:3}, at: kvm_vm_ioctl_set_memory_region+0x62/0xa0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2060
1 lock held by syz-executor.3/8923:
#0: ffffc900037c10a8 (&kvm->slots_lock){+.+.}-{3:3}, at: kvm_set_memory_region arch/x86/kvm/../../../virt/kvm/kvm_main.c:2047 [inline]
#0: ffffc900037c10a8 (&kvm->slots_lock){+.+.}-{3:3}, at: kvm_vm_ioctl_set_memory_region+0x62/0xa0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2060

=============================================

NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.1.91-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x4e1/0x560 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1b0/0x3f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xf88/0xfd0 kernel/hung_task.c:377
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 8826 Comm: syz-executor.4 Not tainted 6.1.91-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:lock_is_held_type+0x1/0x180 kernel/locking/lockdep.c:5690
Code: 75 d6 48 c7 c7 60 00 ec 8a 48 c7 c6 a0 00 ec 8a e8 f4 a1 c7 f6 0f 0b eb bf e8 ab fd ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 55 <41> 57 41 56 41 55 41 54 53 48 83 ec 10 65 48 8b 04 25 28 00 00 00
RSP: 0018:ffffc90000007bf0 EFLAGS: 00000046
RAX: ffffffff81517ec5 RBX: 0000000000000001 RCX: ffff888056dbd940
RDX: 0000000080010002 RSI: 00000000ffffffff RDI: ffffffff8ce0a058
RBP: ffff888056dbc1b8 R08: ffffffff815b3f07 R09: fffffbfff2093845
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff92000000f8c R14: 0000000000000001 R15: 0000000000000001
FS: 00007f77ff15f6c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffff7000000 CR3: 00000000755c8000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
pid_task+0x70/0x140 kernel/pid.c:401
send_sigqueue+0x1c5/0x720 kernel/signal.c:1977
posix_timer_event kernel/time/posix-timers.c:354 [inline]
posix_timer_fn+0x186/0x390 kernel/time/posix-timers.c:380
__run_hrtimer kernel/time/hrtimer.c:1686 [inline]
__hrtimer_run_queues+0x5e5/0xe50 kernel/time/hrtimer.c:1750
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1812
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:__raw_spin_unlock_irq include/linux/spinlock_api_smp.h:160 [inline]
RIP: 0010:_raw_spin_unlock_irq+0x25/0x40 kernel/locking/spinlock.c:202
Code: c1 bc f5 ff 90 53 48 89 fb 48 83 c7 18 48 8b 74 24 08 e8 fe 5b d5 f6 48 89 df e8 66 99 d6 f6 e8 31 24 fc f6 fb bf 01 00 00 00 <e8> 56 28 c9 f6 65 8b 05 c7 43 6d 75 85 c0 74 02 5b c3 e8 f4 68 6b
RSP: 0018:ffffc9000327fb30 EFLAGS: 00000286
RAX: 9722c88853910600 RBX: ffff888027608940 RCX: ffffffff91c94103
RDX: dffffc0000000000 RSI: ffffffff8aec01c0 RDI: 0000000000000001
RBP: ffffc9000327fc70 R08: dffffc0000000000 R09: ffffed1004ec1129
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff11004ec11bb
R13: 000000001c000004 R14: 0000000000000021 R15: ffff888027608dd8
spin_unlock_irq include/linux/spinlock.h:401 [inline]
get_signal+0x154b/0x17d0 kernel/signal.c:2865
arch_do_signal_or_restart+0xb0/0x1a10 arch/x86/kernel/signal.c:871
exit_to_user_mode_loop+0x6a/0x100 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:303
do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f77fe47cee7
Code: 14 25 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 <0f> 05 48 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89
RSP: 002b:00007f77ff15f0c8 EFLAGS: 00000246
RAX: 00000000000000ca RBX: 00007f77fe5abf80 RCX: 00007f77fe47cee9
RDX: 0000000000000000 RSI: 0000800000000006 RDI: 0000000020001300
RBP: 00007f77fe4c949e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f77fe5abf80 R15: 00007ffe681db8c8
</TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages