[v6.1] INFO: task hung in lock_rename
6 views
Skip to first unread message
syzbot
Jun 1, 2023, 2:41:55 AM6/1/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: d2869ace6eeb Linux 6.1.31
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1093d67d280000
kernel config: https://syzkaller.appspot.com/x/.config?x=623aacf949348d7d
dashboard link: https://syzkaller.appspot.com/bug?extid=053bd1c776f16c7ec272
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2ed651ed0d8f/disk-d2869ace.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b8d3199c542c/vmlinux-d2869ace.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a44812549bf7/bzImage-d2869ace.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+053bd1...@syzkaller.appspotmail.com
INFO: task syz-executor.0:3920 blocked for more than 143 seconds.
Not tainted 6.1.31-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:26952 pid:3920 ppid:31638 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x132c/0x4330 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
rwsem_down_write_slowpath+0xe93/0x14a0 kernel/locking/rwsem.c:1189
lock_rename+0x182/0x1a0
do_renameat2+0x545/0x13b0 fs/namei.c:4871
__do_sys_renameat2 fs/namei.c:4963 [inline]
__se_sys_renameat2 fs/namei.c:4960 [inline]
__x64_sys_renameat2+0xce/0xe0 fs/namei.c:4960
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fd46708c169
RSP: 002b:00007fd467e88168 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007fd4671ac050 RCX: 00007fd46708c169
RDX: 0000000000000004 RSI: 00000000200002c0 RDI: 0000000000000004
RBP: 00007fd4670e7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020000180 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff47ac7b8f R14: 00007fd467e88300 R15: 0000000000022000
</TASK>
INFO: task syz-executor.0:3922 blocked for more than 143 seconds.
Not tainted 6.1.31-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:27128 pid:3922 ppid:31638 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x132c/0x4330 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
rwsem_down_write_slowpath+0xe93/0x14a0 kernel/locking/rwsem.c:1189
inode_lock_nested include/linux/fs.h:791 [inline]
ext4_rename fs/ext4/namei.c:3842 [inline]
ext4_rename2+0x1090/0x4410 fs/ext4/namei.c:4221
vfs_rename+0xd8f/0x1190 fs/namei.c:4779
do_renameat2+0xb97/0x13b0 fs/namei.c:4930
__do_sys_rename fs/namei.c:4976 [inline]
__se_sys_rename fs/namei.c:4974 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:4974
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fd46708c169
RSP: 002b:00007fd467e67168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007fd4671ac120 RCX: 00007fd46708c169
RDX: 0000000000000000 RSI: 00000000200000c0 RDI: 0000000020000200
RBP: 00007fd4670e7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff47ac7b8f R14: 00007fd467e67300 R15: 0000000000022000
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cf27470 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:510
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cf27c70 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:510
1 lock held by khungtaskd/28:
#0: ffffffff8cf272a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3300:
#0: ffff8880294b9098 (&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:2177
2 locks held by syz-fuzzer/3537:
#0: ffff88807de86ae8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x250/0x2f0 fs/file.c:1047
#1: ffff888031ab8e08 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: iterate_dir+0x10a/0x560 fs/readdir.c:55
3 locks held by kworker/u4:0/18277:
4 locks held by syz-executor.0/3920:
#0: ffff88807e4ac460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88807e4ac748 (&type->s_vfs_rename_key#2){+.+.}-{3:3}, at: lock_rename+0x54/0x1a0 fs/namei.c:2994
#2: ffff88808c54f258 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: lock_rename+0x13a/0x1a0
#3: ffff888080fb6850 (&type->i_mutex_dir_key#3/5){+.+.}-{3:3}, at: lock_rename+0x182/0x1a0
4 locks held by syz-executor.0/3922:
#0: ffff88807e4ac460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff888031ab8e08 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: lock_rename+0x182/0x1a0
#2: ffff888080fb6850 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
#2: ffff888080fb6850 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: vfs_rename+0x78f/0x1190 fs/namei.c:4751
#3: ffff88808c54f258 (&type->i_mutex_dir_key#3/4){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:791 [inline]
#3: ffff88808c54f258 (&type->i_mutex_dir_key#3/4){+.+.}-{3:3}, at: ext4_rename fs/ext4/namei.c:3842 [inline]
#3: ffff88808c54f258 (&type->i_mutex_dir_key#3/4){+.+.}-{3:3}, at: ext4_rename2+0x1090/0x4410 fs/ext4/namei.c:4221
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.1.31-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
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+0xf18/0xf60 kernel/hung_task.c:377
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 14715 Comm: kworker/u4:77 Not tainted 6.1.31-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
Workqueue: bat_events batadv_nc_worker
RIP: 0010:kasan_check_range+0x3/0x290 mm/kasan/generic.c:188
Code: 48 89 c7 e8 4f 8d a3 08 31 c0 c3 0f 0b b8 ea ff ff ff c3 0f 0b b8 ea ff ff ff c3 cc cc cc cc cc cc cc cc cc cc cc cc 55 41 57 <41> 56 53 b0 01 48 85 f6 0f 84 9a 01 00 00 48 89 fd 48 01 f5 0f 82
RSP: 0018:ffffc90014fdfa68 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff8169d30b
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8e531768
RBP: ffffc90014fdfbd8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff920029fbf58
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff888083ef9b80
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c028689200 CR3: 000000001a719000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
instrument_atomic_read include/linux/instrumented.h:72 [inline]
_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline]
cpumask_test_cpu include/linux/cpumask.h:444 [inline]
cpu_online include/linux/cpumask.h:1030 [inline]
trace_lock_acquire include/trace/events/lock.h:24 [inline]
lock_acquire+0xeb/0x5a0 kernel/locking/lockdep.c:5640
rcu_lock_acquire+0x2a/0x30 include/linux/rcupdate.h:306
rcu_read_lock include/linux/rcupdate.h:747 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:408 [inline]
batadv_nc_worker+0xc1/0x5b0 net/batman-adv/network-coding.c:719
process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2289
worker_thread+0xa5f/0x1210 kernel/workqueue.c:2436
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, 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: d2869ace6eeb Linux 6.1.31
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1093d67d280000
kernel config: https://syzkaller.appspot.com/x/.config?x=623aacf949348d7d
dashboard link: https://syzkaller.appspot.com/bug?extid=053bd1c776f16c7ec272
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2ed651ed0d8f/disk-d2869ace.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b8d3199c542c/vmlinux-d2869ace.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a44812549bf7/bzImage-d2869ace.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+053bd1...@syzkaller.appspotmail.com
INFO: task syz-executor.0:3920 blocked for more than 143 seconds.
Not tainted 6.1.31-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:26952 pid:3920 ppid:31638 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x132c/0x4330 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
rwsem_down_write_slowpath+0xe93/0x14a0 kernel/locking/rwsem.c:1189
lock_rename+0x182/0x1a0
do_renameat2+0x545/0x13b0 fs/namei.c:4871
__do_sys_renameat2 fs/namei.c:4963 [inline]
__se_sys_renameat2 fs/namei.c:4960 [inline]
__x64_sys_renameat2+0xce/0xe0 fs/namei.c:4960
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fd46708c169
RSP: 002b:00007fd467e88168 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007fd4671ac050 RCX: 00007fd46708c169
RDX: 0000000000000004 RSI: 00000000200002c0 RDI: 0000000000000004
RBP: 00007fd4670e7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020000180 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff47ac7b8f R14: 00007fd467e88300 R15: 0000000000022000
</TASK>
INFO: task syz-executor.0:3922 blocked for more than 143 seconds.
Not tainted 6.1.31-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:27128 pid:3922 ppid:31638 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x132c/0x4330 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
rwsem_down_write_slowpath+0xe93/0x14a0 kernel/locking/rwsem.c:1189
inode_lock_nested include/linux/fs.h:791 [inline]
ext4_rename fs/ext4/namei.c:3842 [inline]
ext4_rename2+0x1090/0x4410 fs/ext4/namei.c:4221
vfs_rename+0xd8f/0x1190 fs/namei.c:4779
do_renameat2+0xb97/0x13b0 fs/namei.c:4930
__do_sys_rename fs/namei.c:4976 [inline]
__se_sys_rename fs/namei.c:4974 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:4974
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fd46708c169
RSP: 002b:00007fd467e67168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007fd4671ac120 RCX: 00007fd46708c169
RDX: 0000000000000000 RSI: 00000000200000c0 RDI: 0000000020000200
RBP: 00007fd4670e7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff47ac7b8f R14: 00007fd467e67300 R15: 0000000000022000
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cf27470 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:510
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cf27c70 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:510
1 lock held by khungtaskd/28:
#0: ffffffff8cf272a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3300:
#0: ffff8880294b9098 (&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:2177
2 locks held by syz-fuzzer/3537:
#0: ffff88807de86ae8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x250/0x2f0 fs/file.c:1047
#1: ffff888031ab8e08 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: iterate_dir+0x10a/0x560 fs/readdir.c:55
3 locks held by kworker/u4:0/18277:
4 locks held by syz-executor.0/3920:
#0: ffff88807e4ac460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88807e4ac748 (&type->s_vfs_rename_key#2){+.+.}-{3:3}, at: lock_rename+0x54/0x1a0 fs/namei.c:2994
#2: ffff88808c54f258 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: lock_rename+0x13a/0x1a0
#3: ffff888080fb6850 (&type->i_mutex_dir_key#3/5){+.+.}-{3:3}, at: lock_rename+0x182/0x1a0
4 locks held by syz-executor.0/3922:
#0: ffff88807e4ac460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff888031ab8e08 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: lock_rename+0x182/0x1a0
#2: ffff888080fb6850 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
#2: ffff888080fb6850 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: vfs_rename+0x78f/0x1190 fs/namei.c:4751
#3: ffff88808c54f258 (&type->i_mutex_dir_key#3/4){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:791 [inline]
#3: ffff88808c54f258 (&type->i_mutex_dir_key#3/4){+.+.}-{3:3}, at: ext4_rename fs/ext4/namei.c:3842 [inline]
#3: ffff88808c54f258 (&type->i_mutex_dir_key#3/4){+.+.}-{3:3}, at: ext4_rename2+0x1090/0x4410 fs/ext4/namei.c:4221
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.1.31-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
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+0xf18/0xf60 kernel/hung_task.c:377
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 14715 Comm: kworker/u4:77 Not tainted 6.1.31-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
Workqueue: bat_events batadv_nc_worker
RIP: 0010:kasan_check_range+0x3/0x290 mm/kasan/generic.c:188
Code: 48 89 c7 e8 4f 8d a3 08 31 c0 c3 0f 0b b8 ea ff ff ff c3 0f 0b b8 ea ff ff ff c3 cc cc cc cc cc cc cc cc cc cc cc cc 55 41 57 <41> 56 53 b0 01 48 85 f6 0f 84 9a 01 00 00 48 89 fd 48 01 f5 0f 82
RSP: 0018:ffffc90014fdfa68 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff8169d30b
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8e531768
RBP: ffffc90014fdfbd8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff920029fbf58
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff888083ef9b80
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c028689200 CR3: 000000001a719000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
instrument_atomic_read include/linux/instrumented.h:72 [inline]
_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline]
cpumask_test_cpu include/linux/cpumask.h:444 [inline]
cpu_online include/linux/cpumask.h:1030 [inline]
trace_lock_acquire include/trace/events/lock.h:24 [inline]
lock_acquire+0xeb/0x5a0 kernel/locking/lockdep.c:5640
rcu_lock_acquire+0x2a/0x30 include/linux/rcupdate.h:306
rcu_read_lock include/linux/rcupdate.h:747 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:408 [inline]
batadv_nc_worker+0xc1/0x5b0 net/batman-adv/network-coding.c:719
process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2289
worker_thread+0xa5f/0x1210 kernel/workqueue.c:2436
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot
Jan 1, 2024, 12:54:14 AMJan 1
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages