[v5.15] INFO: task hung in TXN_SLEEP_DROP_LOCK (2)
1 view
Skip to first unread message
syzbot
Oct 15, 2025, 9:59:44 AM (yesterday) Oct 15
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 29e53a5b1c4f Linux 5.15.194
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1655ddcd980000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=a39be290a86cffd6c3fa
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8cd4e3ff852c/disk-29e53a5b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/21e1f773622c/vmlinux-29e53a5b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8f418c0a25cc/bzImage-29e53a5b.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a39be2...@syzkaller.appspotmail.com
INFO: task syz.2.1542:10837 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.2.1542 state:D stack:26928 pid:10837 ppid: 8977 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
io_schedule+0x7c/0xd0 kernel/sched/core.c:8503
TXN_SLEEP_DROP_LOCK+0x110/0x170 fs/jfs/jfs_txnmgr.c:125
txBegin+0x10d/0x650 fs/jfs/jfs_txnmgr.c:-1
jfs_rename+0x50f/0x16a0 fs/jfs/namei.c:1153
vfs_rename+0xbbf/0x10d0 fs/namei.c:4832
do_renameat2+0xa83/0xf70 fs/namei.c:4985
__do_sys_renameat2 fs/namei.c:5018 [inline]
__se_sys_renameat2 fs/namei.c:5015 [inline]
__x64_sys_renameat2+0xce/0xe0 fs/namei.c:5015
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f8da278fec9
RSP: 002b:00007f8da09d6038 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007f8da29e7090 RCX: 00007f8da278fec9
RDX: ffffffffffffff9c RSI: 0000200000005b40 RDI: ffffffffffffff9c
RBP: 00007f8da2812f91 R08: 0000000000000000 R09: 0000000000000000
R10: 00002000000005c0 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f8da29e7128 R14: 00007f8da29e7090 R15: 00007fff6e35d468
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c11c660 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3952:
#0: ffff88814cf1c098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002d032e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
3 locks held by kworker/1:4/4244:
#0: ffff888016870938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc9000321fd00 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8c1210e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#2: ffffffff8c1210e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x320/0x6b0 kernel/rcu/tree_exp.h:845
3 locks held by kworker/u4:6/4318:
3 locks held by kworker/u4:10/4374:
#0: ffff888016879138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc9000349fd00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8d238308 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:251
4 locks held by kworker/u4:14/5494:
#0: ffff8880169cd938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc900031ffd00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8d22c690 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x132/0xb80 net/core/net_namespace.c:589
#3: ffffffff8d238308 (rtnl_mutex){+.+.}-{3:3}, at: netdev_run_todo+0x86b/0xa40 net/core/dev.c:10696
2 locks held by kworker/1:8/6848:
#0: ffff888016872138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc9000438fd00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
2 locks held by syz.2.1542/10837:
#0: ffff88805fadc460 (sb_writers#29){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:377
#1: ffff888052741800 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline]
#1: ffff888052741800 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: do_renameat2+0x42a/0xf70 fs/namei.c:4924
2 locks held by syz-executor/13560:
#0: ffffffff8d238308 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d238308 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x974/0xe60 net/core/rtnetlink.c:5647
#1: ffffffff8c1210e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#1: ffffffff8c1210e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x347/0x6b0 kernel/rcu/tree_exp.h:845
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4372 Comm: kworker/u4:9 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: phy53 ieee80211_iface_work
RIP: 0010:deref_stack_reg+0xf1/0x120 arch/x86/kernel/unwind_orc.c:362
Code: 26 4c 89 f7 e8 90 07 00 00 49 89 c6 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 07 9c 87 00 4c 89 33 b0 01 5b 41 5c <41> 5d 41 5e 41 5f 5d c3 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 5d
RSP: 0018:ffffc9000346f620 EFLAGS: 00000246
RAX: 1ffff9200068de01 RBX: ffffc9000346f768 RCX: 0000000000000001
RDX: ffffc9000346f7a8 RSI: ffffc9000346f758 RDI: ffffc9000346f758
RBP: ffffc90003470000 R08: dffffc0000000000 R09: ffffc9000346f7b8
R10: fffff5200068def9 R11: 1ffff9200068def7 R12: 1ffffffff1bc6613
R13: ffffc90003468000 R14: ffffc9000346f7f0 R15: ffffc9000346f768
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6d566eb1d4 CR3: 0000000071fe8000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
unwind_next_frame+0x115d/0x1d90 arch/x86/kernel/unwind_orc.c:-1
__unwind_start+0x5bb/0x740 arch/x86/kernel/unwind_orc.c:704
unwind_start arch/x86/include/asm/unwind.h:60 [inline]
arch_stack_walk+0xda/0x140 arch/x86/kernel/stacktrace.c:24
stack_trace_save+0x98/0xe0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:46
kasan_set_free_info+0x1f/0x40 mm/kasan/generic.c:360
____kasan_slab_free+0xd5/0x110 mm/kasan/common.c:366
kasan_slab_free include/linux/kasan.h:230 [inline]
slab_free_hook mm/slub.c:1710 [inline]
slab_free_freelist_hook+0xea/0x170 mm/slub.c:1736
slab_free mm/slub.c:3504 [inline]
kmem_cache_free+0x8f/0x210 mm/slub.c:3520
kfree_skb include/linux/skbuff.h:1118 [inline]
ieee80211_iface_work+0x798/0xc60 net/mac80211/iface.c:1515
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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
syzbot found the following issue on:
HEAD commit: 29e53a5b1c4f Linux 5.15.194
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1655ddcd980000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=a39be290a86cffd6c3fa
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8cd4e3ff852c/disk-29e53a5b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/21e1f773622c/vmlinux-29e53a5b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8f418c0a25cc/bzImage-29e53a5b.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a39be2...@syzkaller.appspotmail.com
INFO: task syz.2.1542:10837 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.2.1542 state:D stack:26928 pid:10837 ppid: 8977 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
io_schedule+0x7c/0xd0 kernel/sched/core.c:8503
TXN_SLEEP_DROP_LOCK+0x110/0x170 fs/jfs/jfs_txnmgr.c:125
txBegin+0x10d/0x650 fs/jfs/jfs_txnmgr.c:-1
jfs_rename+0x50f/0x16a0 fs/jfs/namei.c:1153
vfs_rename+0xbbf/0x10d0 fs/namei.c:4832
do_renameat2+0xa83/0xf70 fs/namei.c:4985
__do_sys_renameat2 fs/namei.c:5018 [inline]
__se_sys_renameat2 fs/namei.c:5015 [inline]
__x64_sys_renameat2+0xce/0xe0 fs/namei.c:5015
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f8da278fec9
RSP: 002b:00007f8da09d6038 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007f8da29e7090 RCX: 00007f8da278fec9
RDX: ffffffffffffff9c RSI: 0000200000005b40 RDI: ffffffffffffff9c
RBP: 00007f8da2812f91 R08: 0000000000000000 R09: 0000000000000000
R10: 00002000000005c0 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f8da29e7128 R14: 00007f8da29e7090 R15: 00007fff6e35d468
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c11c660 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3952:
#0: ffff88814cf1c098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002d032e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
3 locks held by kworker/1:4/4244:
#0: ffff888016870938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc9000321fd00 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8c1210e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#2: ffffffff8c1210e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x320/0x6b0 kernel/rcu/tree_exp.h:845
3 locks held by kworker/u4:6/4318:
3 locks held by kworker/u4:10/4374:
#0: ffff888016879138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc9000349fd00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8d238308 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:251
4 locks held by kworker/u4:14/5494:
#0: ffff8880169cd938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc900031ffd00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8d22c690 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x132/0xb80 net/core/net_namespace.c:589
#3: ffffffff8d238308 (rtnl_mutex){+.+.}-{3:3}, at: netdev_run_todo+0x86b/0xa40 net/core/dev.c:10696
2 locks held by kworker/1:8/6848:
#0: ffff888016872138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc9000438fd00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
2 locks held by syz.2.1542/10837:
#0: ffff88805fadc460 (sb_writers#29){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:377
#1: ffff888052741800 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline]
#1: ffff888052741800 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: do_renameat2+0x42a/0xf70 fs/namei.c:4924
2 locks held by syz-executor/13560:
#0: ffffffff8d238308 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d238308 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x974/0xe60 net/core/rtnetlink.c:5647
#1: ffffffff8c1210e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#1: ffffffff8c1210e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x347/0x6b0 kernel/rcu/tree_exp.h:845
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4372 Comm: kworker/u4:9 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: phy53 ieee80211_iface_work
RIP: 0010:deref_stack_reg+0xf1/0x120 arch/x86/kernel/unwind_orc.c:362
Code: 26 4c 89 f7 e8 90 07 00 00 49 89 c6 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 07 9c 87 00 4c 89 33 b0 01 5b 41 5c <41> 5d 41 5e 41 5f 5d c3 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 5d
RSP: 0018:ffffc9000346f620 EFLAGS: 00000246
RAX: 1ffff9200068de01 RBX: ffffc9000346f768 RCX: 0000000000000001
RDX: ffffc9000346f7a8 RSI: ffffc9000346f758 RDI: ffffc9000346f758
RBP: ffffc90003470000 R08: dffffc0000000000 R09: ffffc9000346f7b8
R10: fffff5200068def9 R11: 1ffff9200068def7 R12: 1ffffffff1bc6613
R13: ffffc90003468000 R14: ffffc9000346f7f0 R15: ffffc9000346f768
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6d566eb1d4 CR3: 0000000071fe8000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
unwind_next_frame+0x115d/0x1d90 arch/x86/kernel/unwind_orc.c:-1
__unwind_start+0x5bb/0x740 arch/x86/kernel/unwind_orc.c:704
unwind_start arch/x86/include/asm/unwind.h:60 [inline]
arch_stack_walk+0xda/0x140 arch/x86/kernel/stacktrace.c:24
stack_trace_save+0x98/0xe0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:46
kasan_set_free_info+0x1f/0x40 mm/kasan/generic.c:360
____kasan_slab_free+0xd5/0x110 mm/kasan/common.c:366
kasan_slab_free include/linux/kasan.h:230 [inline]
slab_free_hook mm/slub.c:1710 [inline]
slab_free_freelist_hook+0xea/0x170 mm/slub.c:1736
slab_free mm/slub.c:3504 [inline]
kmem_cache_free+0x8f/0x210 mm/slub.c:3520
kfree_skb include/linux/skbuff.h:1118 [inline]
ieee80211_iface_work+0x798/0xc60 net/mac80211/iface.c:1515
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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