[v5.15] INFO: task hung in lookup_slow (2)

0 views
Skip to first unread message

syzbot

unread,
Apr 15, 2024, 12:02:28 AMApr 15
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: fa3df276cd36 Linux 5.15.155
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17a06c7d180000
kernel config: https://syzkaller.appspot.com/x/.config?x=f12ea3f162537c9c
dashboard link: https://syzkaller.appspot.com/bug?extid=0901bf4880820032b2eb
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/feaf3fb3f68f/disk-fa3df276.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/537c519f1dd0/vmlinux-fa3df276.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5396ec75d1be/bzImage-fa3df276.xz

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

INFO: task syz-executor.4:6774 blocked for more than 144 seconds.
Not tainted 5.15.155-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:27520 pid: 6774 ppid: 5162 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
rwsem_down_read_slowpath+0x605/0xb40 kernel/locking/rwsem.c:1055
__down_read_common kernel/locking/rwsem.c:1239 [inline]
__down_read kernel/locking/rwsem.c:1252 [inline]
down_read+0x9a/0x2e0 kernel/locking/rwsem.c:1500
inode_lock_shared include/linux/fs.h:799 [inline]
lookup_slow+0x45/0x70 fs/namei.c:1679
walk_component+0x48c/0x610 fs/namei.c:1976
lookup_last fs/namei.c:2431 [inline]
path_lookupat+0x16f/0x450 fs/namei.c:2455
filename_lookup+0x230/0x5c0 fs/namei.c:2484
user_path_at_empty+0x40/0x180 fs/namei.c:2883
user_path_at include/linux/namei.h:57 [inline]
do_mount fs/namespace.c:3345 [inline]
__do_sys_mount fs/namespace.c:3556 [inline]
__se_sys_mount+0x296/0x3c0 fs/namespace.c:3533
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fa17cb3fe69
RSP: 002b:00007fa17b0910c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fa17cc6e050 RCX: 00007fa17cb3fe69
RDX: 0000000020002100 RSI: 0000000020000000 RDI: 0000000000000000
RBP: 00007fa17cb8c47a R08: 0000000020000200 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007fa17cc6e050 R15: 00007ffe64a57848
</TASK>
INFO: task syz-executor.4:6776 blocked for more than 145 seconds.
Not tainted 5.15.155-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:28512 pid: 6776 ppid: 5162 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
rwsem_down_read_slowpath+0x605/0xb40 kernel/locking/rwsem.c:1055
__down_read_common kernel/locking/rwsem.c:1239 [inline]
__down_read kernel/locking/rwsem.c:1252 [inline]
down_read+0x9a/0x2e0 kernel/locking/rwsem.c:1500
inode_lock_shared include/linux/fs.h:799 [inline]
lookup_slow+0x45/0x70 fs/namei.c:1679
walk_component+0x48c/0x610 fs/namei.c:1976
lookup_last fs/namei.c:2431 [inline]
path_lookupat+0x16f/0x450 fs/namei.c:2455
filename_lookup+0x230/0x5c0 fs/namei.c:2484
user_path_at_empty+0x40/0x180 fs/namei.c:2883
user_path_at include/linux/namei.h:57 [inline]
do_utimes_path fs/utimes.c:94 [inline]
do_utimes+0x111/0x270 fs/utimes.c:144
__do_sys_utimensat fs/utimes.c:163 [inline]
__se_sys_utimensat fs/utimes.c:147 [inline]
__x64_sys_utimensat+0x14b/0x250 fs/utimes.c:147
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fa17cb3fe69
RSP: 002b:00007fa17b0700c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000118
RAX: ffffffffffffffda RBX: 00007fa17cc6e120 RCX: 00007fa17cb3fe69
RDX: 0000000000000000 RSI: 0000000020000040 RDI: ffffffffffffff9c
RBP: 00007fa17cb8c47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007fa17cc6e120 R15: 00007ffe64a57848
</TASK>
INFO: task syz-executor.4:6782 blocked for more than 146 seconds.
Not tainted 5.15.155-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:28512 pid: 6782 ppid: 5162 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
rwsem_down_write_slowpath+0xf0c/0x16a0 kernel/locking/rwsem.c:1165
inode_lock_nested include/linux/fs.h:824 [inline]
filename_create+0x25c/0x530 fs/namei.c:3835
do_mkdirat+0xb3/0x520 fs/namei.c:4080
__do_sys_mkdirat fs/namei.c:4105 [inline]
__se_sys_mkdirat fs/namei.c:4103 [inline]
__x64_sys_mkdirat+0x85/0x90 fs/namei.c:4103
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fa17cb3e967
RSP: 002b:00007fa17b02def8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007fa17b02df80 RCX: 00007fa17cb3e967
RDX: 00000000000001ff RSI: 0000000020001080 RDI: 00000000ffffff9c
RBP: 0000000020000040 R08: 0000000020006380 R09: 0000000000000000
R10: 0000000020000040 R11: 0000000000000246 R12: 0000000020001080
R13: 00007fa17b02df40 R14: 0000000000000000 R15: 0000000000000000
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/26:
#0: ffffffff8c91fae0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
3 locks held by kworker/1:2/1069:
#0: ffff888011c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc90004c57d20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffffffff8c9240a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#2: ffffffff8c9240a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x350/0x740 kernel/rcu/tree_exp.h:845
1 lock held by udevd/2961:
#0: ffff8880b9b3a358 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
1 lock held by dhcpcd/3173:
#0: ffffffff8d9e75c8 (rtnl_mutex){+.+.}-{3:3}, at: __netlink_dump_start+0x12e/0x6f0 net/netlink/af_netlink.c:2348
2 locks held by getty/3255:
#0: ffff8880246dc098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002bab2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
3 locks held by kworker/u5:2/3522:
#0: ffff8880547f3938 ((wq_completion)hci1){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc90002d97d20 ((work_completion)(&hdev->error_reset)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffff88807942cff0 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_open+0xa4/0x1330 net/bluetooth/hci_core.c:1446
2 locks held by kworker/0:3/3529:
#0: ffff888011c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc90002e17d20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
4 locks held by kworker/u4:8/4328:
#0: ffff888011dcd138 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc90002df7d20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffffffff8d9dba10 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf1/0xb60 net/core/net_namespace.c:558
#3: ffffffff8d9e75c8 (rtnl_mutex){+.+.}-{3:3}, at: cangw_pernet_exit+0xe/0x20 net/can/gw.c:1244
2 locks held by kworker/0:19/4910:
#0: ffff888011c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc90003817d20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
2 locks held by kworker/1:19/5460:
#0: ffff888011c72138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc90003b8fd20 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
3 locks held by syz-executor.4/6764:
1 lock held by syz-executor.4/6774:
#0: ffff88805dd0c188 (&type->i_mutex_dir_key#23){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff88805dd0c188 (&type->i_mutex_dir_key#23){.+.+}-{3:3}, at: lookup_slow+0x45/0x70 fs/namei.c:1679
1 lock held by syz-executor.4/6776:
#0: ffff88805dd0c188 (&type->i_mutex_dir_key#23){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff88805dd0c188 (&type->i_mutex_dir_key#23){.+.+}-{3:3}, at: lookup_slow+0x45/0x70 fs/namei.c:1679
2 locks held by syz-executor.4/6782:
#0: ffff888061180460 (sb_writers#30){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
#1: ffff88805dd0c188 (&type->i_mutex_dir_key#22/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline]
#1: ffff88805dd0c188 (&type->i_mutex_dir_key#22/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3835
2 locks held by syz-executor.2/7763:
#0: ffff88801b4bd118 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xfb/0x790 block/bdev.c:912
#1: ffff88801b4b2468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa9/0xbe0 drivers/block/loop.c:1365
2 locks held by syz-executor.3/9392:
#0: ffffffff8d9e75c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9e75c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5626
#1: ffffffff8c9240a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#1: ffffffff8c9240a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x280/0x740 kernel/rcu/tree_exp.h:845
1 lock held by dhcpcd/9526:
#0: ffff88801d8f6120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1668 [inline]
#0: ffff88801d8f6120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x33/0xd50 net/packet/af_packet.c:3164
1 lock held by dhcpcd/9527:
#0: ffff8880151a8120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1668 [inline]
#0: ffff8880151a8120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x33/0xd50 net/packet/af_packet.c:3164
1 lock held by dhcpcd/9528:
#0: ffff8880577b2120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1668 [inline]
#0: ffff8880577b2120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x33/0xd50 net/packet/af_packet.c:3164
1 lock held by dhcpcd/9529:
#0: ffff8880773a0120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1668 [inline]
#0: ffff8880773a0120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x33/0xd50 net/packet/af_packet.c:3164
1 lock held by dhcpcd/9531:
#0: ffff888019fa2120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1668 [inline]
#0: ffff888019fa2120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x33/0xd50 net/packet/af_packet.c:3164
1 lock held by dhcpcd/9532:
#0: ffff888023d74120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1668 [inline]
#0: ffff888023d74120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x33/0xd50 net/packet/af_packet.c:3164
1 lock held by syz-executor.4/9534:
#0: ffffffff8d9e75c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9e75c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5626
2 locks held by syz-executor.1/9542:
#0: ffff88801b4b8918 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xfb/0x790 block/bdev.c:912
#1: ffff888147717468 (&lo->lo_mutex){+.+.}-{3:3}, at: lo_release+0x4d/0x1f0 drivers/block/loop.c:2070

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

NMI backtrace for cpu 0
CPU: 0 PID: 26 Comm: khungtaskd Not tainted 5.15.155-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 6764 Comm: syz-executor.4 Not tainted 5.15.155-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:bytes_is_nonzero mm/kasan/generic.c:85 [inline]
RIP: 0010:memory_is_nonzero mm/kasan/generic.c:102 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:128 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:159 [inline]
RIP: 0010:check_region_inline mm/kasan/generic.c:180 [inline]
RIP: 0010:kasan_check_range+0x7b/0x290 mm/kasan/generic.c:189
Code: 00 00 00 00 fc ff df 4f 8d 34 1a 4c 89 f5 4c 29 cd 48 83 fd 10 7f 26 48 85 ed 0f 84 3a 01 00 00 49 f7 d2 49 01 da 41 80 39 00 <0f> 85 c4 01 00 00 49 ff c1 49 ff c2 75 ee e9 1d 01 00 00 45 89 cf
RSP: 0018:ffffc90003017218 EFLAGS: 00000046
RAX: 0000000000000001 RBX: 1ffffffff1bc8b65 RCX: ffffffff8162ac8c
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8de45b28
RBP: 0000000000000001 R08: dffffc0000000000 R09: fffffbfff1bc8b65
R10: ffffffffffffffff R11: dffffc0000000001 R12: 1ffff92000602e50
R13: dffffc0000000000 R14: fffffbfff1bc8b66 R15: dffffc0000000000
FS: 00007fa17b0b26c0(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000002000a000 CR3: 0000000076e8a000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
instrument_atomic_read include/linux/instrumented.h:71 [inline]
test_bit include/asm-generic/bitops/instrumented-non-atomic.h:134 [inline]
cpumask_test_cpu include/linux/cpumask.h:344 [inline]
cpu_online include/linux/cpumask.h:895 [inline]
trace_lock_acquire include/trace/events/lock.h:13 [inline]
lock_acquire+0xcc/0x4f0 kernel/locking/lockdep.c:5594
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0xd1/0x120 kernel/locking/spinlock.c:162
__unfreeze_partials+0x97/0x210 mm/slub.c:2471
put_cpu_partial+0x132/0x1a0 mm/slub.c:2587
do_slab_free mm/slub.c:3487 [inline]
___cache_free+0xe3/0x100 mm/slub.c:3506
qlist_free_all+0x36/0x90 mm/kasan/quarantine.c:176
kasan_quarantine_reduce+0x162/0x180 mm/kasan/quarantine.c:283
__kasan_slab_alloc+0x2f/0xc0 mm/kasan/common.c:444
kasan_slab_alloc include/linux/kasan.h:254 [inline]
slab_post_alloc_hook+0x53/0x380 mm/slab.h:519
slab_alloc_node mm/slub.c:3220 [inline]
slab_alloc mm/slub.c:3228 [inline]
kmem_cache_alloc+0xf3/0x280 mm/slub.c:3233
kmem_cache_zalloc include/linux/slab.h:711 [inline]
alloc_buffer_head+0x20/0xf0 fs/buffer.c:3311
alloc_page_buffers+0x3a3/0x660 fs/buffer.c:832
create_empty_buffers+0x3a/0x6d0 fs/buffer.c:1562
create_page_buffers+0x1d4/0x330 fs/buffer.c:1679
block_read_full_page+0xe6/0xde0 fs/buffer.c:2270
do_read_cache_page+0x752/0x1040
read_mapping_page include/linux/pagemap.h:515 [inline]
dir_get_page fs/sysv/dir.c:58 [inline]
sysv_find_entry+0x1b0/0x650 fs/sysv/dir.c:146
sysv_inode_by_name+0x9e/0x3f0 fs/sysv/dir.c:360
sysv_lookup+0x63/0xe0 fs/sysv/namei.c:38
lookup_one_qstr_excl+0x117/0x240 fs/namei.c:1563
filename_create+0x293/0x530 fs/namei.c:3836
do_mkdirat+0xb3/0x520 fs/namei.c:4080
__do_sys_mkdirat fs/namei.c:4105 [inline]
__se_sys_mkdirat fs/namei.c:4103 [inline]
__x64_sys_mkdirat+0x85/0x90 fs/namei.c:4103
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fa17cb3e967
Code: 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 02 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa17b0b1ef8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007fa17b0b1f80 RCX: 00007fa17cb3e967
RDX: 00000000000001ff RSI: 00000000200000c0 RDI: 00000000ffffff9c
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000200000c0
R13: 00007fa17b0b1f40 R14: 0000000000000000 R15: 0000000000000000
</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