[v6.6] INFO: task hung in do_renameat2

0 views
Skip to first unread message

syzbot

unread,
9:18 AM (11 hours ago) 9:18 AM
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c09fbcd31ae6 Linux 6.6.130
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16a2546a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c5b35c4db8465904
dashboard link: https://syzkaller.appspot.com/bug?extid=8a4738fbda1bc5064745
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/58165bbf9941/disk-c09fbcd3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/73cbb84fb36b/vmlinux-c09fbcd3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/744ea33ec44b/bzImage-c09fbcd3.xz

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

INFO: task syz.1.610:8364 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.1.610 state:D stack:27624 pid:8364 ppid:5776 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x1553/0x45a0 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6833
rwsem_down_write_slowpath+0xc05/0xff0 kernel/locking/rwsem.c:1178
__down_write_common kernel/locking/rwsem.c:1306 [inline]
__down_write kernel/locking/rwsem.c:1315 [inline]
down_write_nested+0x1c3/0x200 kernel/locking/rwsem.c:1690
lock_rename include/linux/fs.h:-1 [inline]
do_renameat2+0x439/0xce0 fs/namei.c:4972
__do_sys_rename fs/namei.c:5079 [inline]
__se_sys_rename fs/namei.c:5077 [inline]
__x64_sys_rename+0x86/0x90 fs/namei.c:5077
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fe514b9c819
RSP: 002b:00007fe515a57028 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007fe514e16270 RCX: 00007fe514b9c819
RDX: 0000000000000000 RSI: 0000200000000580 RDI: 0000200000000840
RBP: 00007fe514c32c91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fe514e16308 R14: 00007fe514e16270 R15: 00007ffc80b50208
</TASK>
INFO: task syz.1.610:8365 blocked for more than 145 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.1.610 state:D stack:26888 pid:8365 ppid:5776 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x1553/0x45a0 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6833
rwsem_down_write_slowpath+0xc05/0xff0 kernel/locking/rwsem.c:1178
__down_write_common kernel/locking/rwsem.c:1306 [inline]
__down_write kernel/locking/rwsem.c:1315 [inline]
down_write_nested+0x1c3/0x200 kernel/locking/rwsem.c:1690
lock_rename include/linux/fs.h:-1 [inline]
do_renameat2+0x439/0xce0 fs/namei.c:4972
__do_sys_renameat2 fs/namei.c:5066 [inline]
__se_sys_renameat2 fs/namei.c:5063 [inline]
__x64_sys_renameat2+0xd2/0xe0 fs/namei.c:5063
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fe514b9c819
RSP: 002b:00007fe515a36028 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007fe514e16360 RCX: 00007fe514b9c819
RDX: ffffffffffffff9c RSI: 0000200000000380 RDI: 000000000000000b
RBP: 00007fe514c32c91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000200000000100 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fe514e163f8 R14: 00007fe514e16360 R15: 00007ffc80b50208
</TASK>

Showing all locks held in the system:
2 locks held by kworker/u4:1/12:
#0: ffff8880b8e3c018 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:559
#1: ffffc90000117d00 ((work_completion)(&(&nsim_dev->trap_data->trap_report_dw)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#1: ffffc90000117d00 ((work_completion)(&(&nsim_dev->trap_data->trap_report_dw)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x96f/0x15d0 kernel/workqueue.c:2730
1 lock held by khungtaskd/29:
#0: ffffffff8d1320a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8d1320a0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8d1320a0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
4 locks held by kworker/u4:9/3486:
#0: ffff88814005d938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#0: ffff88814005d938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_scheduled_works+0x96f/0x15d0 kernel/workqueue.c:2730
#1: ffffc9000d15fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#1: ffffc9000d15fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x96f/0x15d0 kernel/workqueue.c:2730
#2: ffff88807ee540e0 (&type->s_umount_key#111){++++}-{3:3}, at: super_trylock_shared+0x20/0xf0 fs/super.c:607
#3: ffff888055645e48 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x1cb/0x520 fs/jfs/inode.c:108
2 locks held by getty/5527:
#0: ffff88802d7560a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000326e2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x433/0x1390 drivers/tty/n_tty.c:2217
3 locks held by kworker/0:7/6205:
#0: ffff888017c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#0: ffff888017c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0x96f/0x15d0 kernel/workqueue.c:2730
#1: ffffc9000bc17d00 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#1: ffffc9000bc17d00 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_scheduled_works+0x96f/0x15d0 kernel/workqueue.c:2730
#2: ffff888140ab6240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x286/0x31b0 drivers/net/netdevsim/fib.c:1491
4 locks held by syz.1.610/8355:
2 locks held by syz.1.610/8364:
#0: ffff88807ee54418 (sb_writers#30){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:412
#1: ffff888055646210 (&type->i_mutex_dir_key#19/1){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline]
#1: ffff888055646210 (&type->i_mutex_dir_key#19/1){+.+.}-{3:3}, at: do_renameat2+0x439/0xce0 fs/namei.c:4972
2 locks held by syz.1.610/8365:
#0: ffff88807ee54418 (sb_writers#30){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:412
#1: ffff888055646210 (&type->i_mutex_dir_key#19/1){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline]
#1: ffff888055646210 (&type->i_mutex_dir_key#19/1){+.+.}-{3:3}, at: do_renameat2+0x439/0xce0 fs/namei.c:4972

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

NMI backtrace for cpu 1
CPU: 1 PID: 29 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Call Trace:
<TASK>
dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
nmi_cpu_backtrace+0x3a6/0x3e0 lib/nmi_backtrace.c:113
nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
watchdog+0xf3d/0xf80 kernel/hung_task.c:379
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 3441 Comm: kworker/u4:7 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Workqueue: events_unbound nsim_dev_trap_report_work
RIP: 0010:debug_spin_lock_before kernel/locking/spinlock_debug.c:85 [inline]
RIP: 0010:do_raw_spin_lock+0x84/0x2c0 kernel/locking/spinlock_debug.c:114
Code: 03 48 b8 f1 f1 f1 f1 f8 f3 f3 f3 4b 89 04 2c 4c 8d 77 04 4c 89 f0 48 c1 e8 03 42 0f b6 04 28 84 c0 0f 85 c3 01 00 00 41 8b 06 <3d> ad 4e ad de 0f 85 14 01 00 00 4c 8d 7b 10 4d 89 fe 49 c1 ee 03
RSP: 0018:ffffc9000cbbf780 EFLAGS: 00000046
RAX: 00000000dead4ead RBX: ffffffff974f18a8 RCX: 34b8493411434e00
RDX: 0000000000000000 RSI: ffffffff8acadb60 RDI: ffffffff974f18a8
RBP: ffffc9000cbbf830 R08: dffffc0000000000 R09: 1ffffffff22386a0
R10: dffffc0000000000 R11: fffffbfff22386a1 R12: 1ffff92001977ef4
R13: dffffc0000000000 R14: ffffffff974f18ac R15: 1ffff92001977f08
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd242f2b7d0 CR3: 000000001b3de000 CR4: 00000000003506f0
Call Trace:
<TASK>
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:111 [inline]
_raw_spin_lock_irqsave+0xc0/0x100 kernel/locking/spinlock.c:162
__debug_check_no_obj_freed lib/debugobjects.c:979 [inline]
debug_check_no_obj_freed+0x13a/0x540 lib/debugobjects.c:1020
slab_free_hook mm/slub.c:1786 [inline]
slab_free_freelist_hook+0xd2/0x1a0 mm/slub.c:1837
slab_free mm/slub.c:3830 [inline]
__kmem_cache_free+0xba/0x1e0 mm/slub.c:3843
skb_kfree_head net/core/skbuff.c:949 [inline]
skb_free_head net/core/skbuff.c:961 [inline]
skb_release_data+0x634/0x800 net/core/skbuff.c:991
skb_release_all net/core/skbuff.c:1057 [inline]
__kfree_skb net/core/skbuff.c:1071 [inline]
consume_skb+0xb2/0x110 net/core/skbuff.c:1287
nsim_dev_trap_report drivers/net/netdevsim/dev.c:821 [inline]
nsim_dev_trap_report_work+0x76f/0xb00 drivers/net/netdevsim/dev.c:851
process_one_work kernel/workqueue.c:2653 [inline]
process_scheduled_works+0xa5d/0x15d0 kernel/workqueue.c:2730
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2811
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</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