[v6.6] INFO: rcu detected stall in dentry_kill

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2cf6f68313dc Linux 6.6.122
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1369bbfa580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2a950bf7c0bff9f9
dashboard link: https://syzkaller.appspot.com/bug?extid=40ef4113d0cb4e05dc9b
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/1694df1122d6/disk-2cf6f683.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d59542417f4c/vmlinux-2cf6f683.xz
kernel image: https://storage.googleapis.com/syzbot-assets/220dc2f6e7ef/bzImage-2cf6f683.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P16854/1:b..l
rcu: (detected by 0, t=10502 jiffies, g=120249, q=239 ncpus=2)
task:syz.1.3091 state:R running task stack:22888 pid:16854 ppid:12775 flags:0x00004002
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x1553/0x45a0 kernel/sched/core.c:6700
preempt_schedule_irq+0xbf/0x150 kernel/sched/core.c:7010
irqentry_exit+0x67/0x70 kernel/entry/common.c:438
asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:687
RIP: 0010:stack_trace_consume_entry+0x56/0x270 kernel/stacktrace.c:89
Code: 84 c0 0f 85 04 01 00 00 44 8b 4f 10 4c 8d 77 08 4d 89 f5 49 c1 ed 03 41 0f b6 44 15 00 84 c0 0f 85 1d 01 00 00 45 3b 0e 73 3a <48> 8d 5f 0c 49 89 df 49 c1 ef 03 41 0f b6 04 17 84 c0 0f 85 42 01
RSP: 0018:ffffc9000469ee78 EFLAGS: 00000283
RAX: 0000000000000000 RBX: ffffc9000469ef80 RCX: ffff88802d4a9e00
RDX: dffffc0000000000 RSI: ffffffff8151e62b RDI: ffffc9000469ef80
RBP: 1ffff920008d3df2 R08: ffffc9000469ef90 R09: 000000000000000d
R10: 0000000000000004 R11: 0000000000000000 R12: ffffffff8151e62b
R13: 1ffff920008d3df1 R14: ffffc9000469ef88 R15: ffffc9000469eec8
arch_stack_walk+0x138/0x190 arch/x86/kernel/stacktrace.c:27
stack_trace_save+0xaa/0x100 kernel/stacktrace.c:122
save_stack+0x125/0x230 mm/page_owner.c:128
__reset_page_owner+0x4e/0x190 mm/page_owner.c:149
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1181 [inline]
free_unref_page_prepare+0x7b2/0x8c0 mm/page_alloc.c:2365
free_unref_page_list+0xbe/0x860 mm/page_alloc.c:2504
release_pages+0x1f7a/0x2200 mm/swap.c:1022
__folio_batch_release+0x71/0xe0 mm/swap.c:1042
folio_batch_release include/linux/pagevec.h:83 [inline]
shmem_undo_range+0x630/0x1b20 mm/shmem.c:1026
shmem_truncate_range mm/shmem.c:1135 [inline]
shmem_evict_inode+0x245/0x9e0 mm/shmem.c:1264
evict+0x4ca/0x8d0 fs/inode.c:705
__dentry_kill+0x431/0x650 fs/dcache.c:611
dentry_kill+0xb8/0x290 fs/dcache.c:-1
dput+0xfe/0x1e0 fs/dcache.c:918
__fput+0x5e5/0x970 fs/file_table.c:392
task_work_run+0x1d4/0x260 kernel/task_work.c:245
exit_task_work include/linux/task_work.h:43 [inline]
do_exit+0x95a/0x2460 kernel/exit.c:883
do_group_exit+0x21b/0x2d0 kernel/exit.c:1024
get_signal+0x12fc/0x13f0 kernel/signal.c:2902
arch_do_signal_or_restart+0xc2/0x800 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:210
irqentry_exit_to_user_mode+0x9/0x30 kernel/entry/common.c:315
exc_page_fault+0x8c/0x100 arch/x86/mm/fault.c:1519
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:608
RIP: 0033:0x7f4a4b19aec1
RSP: 002b:fffffffffffffc70 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007f4a4b415fa0 RCX: 00007f4a4b19aeb9
RDX: 0000000000000000 RSI: fffffffffffffc70 RDI: 0000000001022000
RBP: 00007f4a4b208c1f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000
R13: 00007f4a4b416038 R14: 00007f4a4b415fa0 R15: 00007ffcc047f098
</TASK>
rcu: rcu_preempt kthread starved for 10390 jiffies! g120249 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=0
rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
rcu: RCU grace-period kthread stack dump:
task:rcu_preempt state:R running task stack:27000 pid:17 ppid:2 flags:0x00004000
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_timeout+0x188/0x2d0 kernel/time/timer.c:2168
rcu_gp_fqs_loop+0x313/0x1590 kernel/rcu/tree.c:1667
rcu_gp_kthread+0x9d/0x3b0 kernel/rcu/tree.c:1866
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>
rcu: Stack dump where RCU GP kthread last ran:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:pv_native_safe_halt+0xf/0x10 arch/x86/kernel/paravirt.c:148
Code: f8 22 02 c3 cc cc cc cc cc cc cc f3 0f 1e fa 0f 0b 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 66 90 0f 00 2d 33 02 44 00 fb f4 <c3> 66 0f 1f 00 55 41 57 41 56 41 54 53 50 8b 2f eb 2e 41 89 de 80
RSP: 0018:ffffffff8ce07d80 EFLAGS: 000002c2
RAX: a44c7b729d873d00 RBX: ffffffff8162a490 RCX: a44c7b729d873d00
RDX: 0000000000000001 RSI: ffffffff8acac900 RDI: ffffffff8b1c81e0
RBP: ffffffff8ce07eb8 R08: ffff8880b8e36b2b R09: 1ffff110171c6d65
R10: dffffc0000000000 R11: ffffed10171c6d66 R12: 1ffffffff19d2688
R13: 1ffffffff19c0fbc R14: 0000000000000000 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcb5d325e80 CR3: 000000001ffe4000 CR4: 00000000003506f0
Call Trace:
<TASK>
arch_safe_halt arch/x86/include/asm/paravirt.h:108 [inline]
default_idle+0x13/0x20 arch/x86/kernel/process.c:753
default_idle_call+0x6c/0xa0 kernel/sched/idle.c:97
cpuidle_idle_call kernel/sched/idle.c:170 [inline]
do_idle+0x1f0/0x4e0 kernel/sched/idle.c:282
cpu_startup_entry+0x43/0x60 kernel/sched/idle.c:380
rest_init+0x2e2/0x300 init/main.c:744
arch_call_rest_init+0xe/0x10 init/main.c:841
start_kernel+0x459/0x4e0 init/main.c:1086
x86_64_start_reservations+0x2a/0x30 arch/x86/kernel/head64.c:555
x86_64_start_kernel+0x60/0x60 arch/x86/kernel/head64.c:536
secondary_startup_64_no_verify+0x179/0x17b
</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