[v6.1] INFO: task hung in reiserfs_readdir_inode

0 views
Skip to first unread message

syzbot

unread,
Dec 10, 2025, 9:02:25 AM (yesterday) Dec 10
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 50cbba13faa2 Linux 6.1.159
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=157c3a1a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a5cbd268406bf43
dashboard link: https://syzkaller.appspot.com/bug?extid=e1cc531260264d138a34
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1706b992580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1105deb4580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/50ceb00b1b39/disk-50cbba13.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ebb8883b9a29/vmlinux-50cbba13.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7edc2a795f03/bzImage-50cbba13.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/4f0657f19867/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1306b992580000)

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

INFO: task syz-executor:4448 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D
stack:21920 pid:4448 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5244 [inline]
__schedule+0x10ec/0x40b0 kernel/sched/core.c:6561
schedule+0xb9/0x180 kernel/sched/core.c:6637
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6696
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x555/0xaf0 kernel/locking/mutex.c:747
reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
reiserfs_readdir_inode+0x164/0x1230 fs/reiserfs/dir.c:79
iterate_dir+0x218/0x560 fs/readdir.c:-1
__do_sys_getdents64 fs/readdir.c:369 [inline]
__se_sys_getdents64+0xe5/0x260 fs/readdir.c:354
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fd0c7bc20b3
RSP: 002b:00007ffce91ed948 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 00005555812da600 RCX: 00007fd0c7bc20b3
RDX: 0000000000008000 RSI: 00005555812da600 RDI: 0000000000000005
RBP: 00005555812da5d4 R08: 0000000000028a41 R09: 0000000000000000
R10: 00007fd0c7dbacc0 R11: 0000000000000293 R12: ffffffffffffffa8
R13: 0000000000000010 R14: 00005555812da5d0 R15: 00007ffce91efc00
</TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8c92bab0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0:
ffffffff8c92c2d0
(
rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/27:
#0: ffffffff8c92b120 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8c92b120 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8c92b120 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6513
3 locks held by kworker/u4:2/40:
3 locks held by kworker/1:1/41:
#0:
ffff88802f305938 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc90000b27d00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#2:
ffffffff8db3b3a8
(
rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xc4/0x14d0 net/ipv6/addrconf.c:4131
3 locks held by kworker/0:2/127:
#0: ffff88802f305938 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1:
ffffc90002d57d00
((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#2: ffffffff8db3b3a8 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xc4/0x14d0 net/ipv6/addrconf.c:4131
4 locks held by kworker/1:2/2119:
#0: ffff888017471138 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc90005667d00 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#2: ffff88807df940e0
(
&type->s_umount_key
#52
){++++}-{3:3}, at: flush_old_commits+0xc8/0x2f0 fs/reiserfs/super.c:97
#3: ffff88805773e090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
2 locks held by getty/4024:
#0: ffff88814d2f6098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1:
ffffc9000327b2f0
(&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x41b/0x1380 drivers/tty/n_tty.c:2198
2 locks held by kworker/0:4/4325:
#0:
ffff888017472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc90003ed7d00
(
(work_completion)(&rew->rew_work)
){+.+.}-{0:0}
, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
4 locks held by kworker/1:5/4346:
#0:
ffff888017471138 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc900032d7d00 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#2:
ffff88801f2700e0
(&type->s_umount_key#52){++++}-{3:3}, at: flush_old_commits+0xc8/0x2f0 fs/reiserfs/super.c:97
#3:
ffff88807991c090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
4 locks held by kworker/0:10/4440:
#0: ffff888017471138 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc90003497d00 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}
, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#2:
ffff8880727340e0 (&type->s_umount_key#52){++++}-{3:3}, at: flush_old_commits+0xc8/0x2f0 fs/reiserfs/super.c:97
#3:
ffff88807d616090
(&sbi->lock
){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
4 locks held by kworker/0:13/4443:
#0: ffff888017471138 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc900034c7d00 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#2: ffff88801af3c0e0 (&type->s_umount_key#52){++++}-{3:3}, at: flush_old_commits+0xc8/0x2f0 fs/reiserfs/super.c:97
#3:
ffff88805dcd7090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
3 locks held by syz-executor/4448:
#0:
ffff88807bbacd68
(
&f->f_pos_lock
){+.+.}-{3:3}
, at: __fdget_pos+0x2ae/0x360 fs/file.c:1038
#1:
ffff88805cdb02e0
(&type->i_mutex_dir_key#8){++++}-{3:3}, at: iterate_dir+0x10d/0x560 fs/readdir.c:55
#2: ffff88807d616090
(&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
3 locks held by syz.1.20/4467:
3 locks held by syz-executor/4604:
#0:
ffff888078da0d68
(&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2ae/0x360 fs/file.c:1038
#1:
ffff88805ccb9020 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: iterate_dir+0x10d/0x560 fs/readdir.c:55
#2:
ffff88805dcd7090 (&sbi->lock
){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
3 locks held by syz.2.22/4637:
6 locks held by syz.4.27/4886:
3 locks held by syz-executor/5199:
#0: ffff88807df94460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:402
#1: ffff88805cdb1d60 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
#1: ffff88805cdb1d60 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: do_unlinkat+0x178/0x560 fs/namei.c:4381
#2: ffff88805ccbb7e0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#2: ffff88805ccbb7e0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: vfs_unlink+0xee/0x600 fs/namei.c:4319
3 locks held by syz.7.35/5311:
2 locks held by syz-executor/5421:
#0:
ffffffff8db3b3a8
(
rtnl_mutex
){+.+.}-{3:3}
, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
, at: rtnetlink_rcv_msg+0x740/0xed0 net/core/rtnetlink.c:6147
#1:
ffff88807a5a93e8
(
&wg->device_update_lock
){+.+.}-{3:3}
, at: wg_open+0x223/0x420 drivers/net/wireguard/device.c:49
2 locks held by dhcpcd/5502:
#0: ffff888072fec130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1792 [inline]
#0: ffff888072fec130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x32/0xce0 net/packet/af_packet.c:3248
#1: ffffffff8c930df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:291 [inline]
#1: ffffffff8c930df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x455/0x830 kernel/rcu/tree_exp.h:962
2 locks held by dhcpcd/5503:
#0: ffff8880768aa130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1792 [inline]
#0: ffff8880768aa130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x32/0xce0 net/packet/af_packet.c:3248
#1: ffffffff8c930df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#1: ffffffff8c930df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x346/0x830 kernel/rcu/tree_exp.h:962
1 lock held by dhcpcd/5504:
#0: ffff88807322c130
(
sk_lock-AF_PACKET
){+.+.}-{0:0}
, at: lock_sock include/net/sock.h:1792 [inline]
, at: packet_do_bind+0x32/0xce0 net/packet/af_packet.c:3248
1 lock held by dhcpcd/5505:
#0: ffff88802706e130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1792 [inline]
#0: ffff88802706e130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x32/0xce0 net/packet/af_packet.c:3248

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
nmi_cpu_backtrace+0x3f4/0x470 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1d4/0x450 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+0xeee/0xf30 kernel/hung_task.c:377
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4362 Comm: kworker/u4:5 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: phy21 ieee80211_iface_work
RIP: 0010:arch_static_branch arch/x86/include/asm/jump_label.h:27 [inline]
RIP: 0010:static_key_false include/linux/jump_label.h:207 [inline]
RIP: 0010:native_write_msr arch/x86/include/asm/msr.h:147 [inline]
RIP: 0010:wrmsr arch/x86/include/asm/msr.h:254 [inline]
RIP: 0010:native_apic_msr_write+0x35/0x50 arch/x86/include/asm/apic.h:206
Code: 74 2a 83 ff 30 74 25 eb 10 81 ff d0 00 00 00 74 1b 81 ff e0 00 00 00 74 13 c1 ef 04 81 c7 00 08 00 00 89 f9 89 f0 31 d2 0f 30 <66> 90 c3 89 f6 31 d2 e9 7f e8 f7 02 66 2e 0f 1f 84 00 00 00 00 00
RSP: 0018:ffffc900001e0e38 EFLAGS: 00000046
RAX: 0000000000021ee7 RBX: 0000000000021ee7 RCX: 0000000000000838
RDX: 0000000000000000 RSI: 0000000000021ee7 RDI: 0000000000000838
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffffbfff1bfe1c6
R10: fffffbfff1bfe1c6 R11: 1ffffffff1bfe1c5 R12: dffffc0000000000
R13: 0000000010009a59 R14: ffffffff8c3d8b40 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056488fe74950 CR3: 000000007a149000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
apic_write arch/x86/include/asm/apic.h:394 [inline]
lapic_next_event+0x5b/0x70 arch/x86/kernel/apic/apic.c:478
clockevents_program_event+0x1bc/0x310 kernel/time/clockevents.c:334
hrtimer_interrupt+0x59d/0x9c0 kernel/time/hrtimer.c:1886
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1107 [inline]
__sysvec_apic_timer_interrupt+0x153/0x5a0 arch/x86/kernel/apic/apic.c:1124
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1118 [inline]
sysvec_apic_timer_interrupt+0x9b/0xc0 arch/x86/kernel/apic/apic.c:1118
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:console_trylock_spinning kernel/printk/printk.c:1948 [inline]
RIP: 0010:vprintk_emit+0x461/0x680 kernel/printk/printk.c:2302
Code: 85 8f 01 00 00 e8 af b9 1a 00 41 89 df 4d 85 f6 48 8b 1c 24 75 07 e8 9e b9 1a 00 eb 06 e8 97 b9 1a 00 fb 48 c7 c7 c0 f3 91 8c <31> f6 ba 01 00 00 00 31 c9 41 b8 01 00 00 00 45 31 c9 53 e8 37 db
RSP: 0018:ffffc900033578a0 EFLAGS: 00000293
RAX: ffffffff81662639 RBX: ffffffff816624e5 RCX: ffff88807b849dc0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff8c91f3c0
RBP: ffffc90003357990 R08: dffffc0000000000 R09: fffffbfff2119055
R10: fffffbfff2119055 R11: 1ffffffff2119054 R12: dffffc0000000000
R13: 1ffff9200066af18 R14: 0000000000000200 R15: 000000000000003f
_printk+0xcc/0x110 kernel/printk/printk.c:2328
ieee80211_sta_find_ibss net/mac80211/ibss.c:1476 [inline]
ieee80211_ibss_work+0xdb8/0x10b0 net/mac80211/ibss.c:1705
process_one_work+0x898/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1250 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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