[v6.1] INFO: rcu detected stall in dput (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 88690811da69 Linux 6.1.92
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16e9ecb4980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ee57a613e7f5bf6c
dashboard link: https://syzkaller.appspot.com/bug?extid=883c06f8852b37453ea8
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8b45ba80e02a/disk-88690811.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ca769d644800/vmlinux-88690811.xz
kernel image: https://storage.googleapis.com/syzbot-assets/26a1d8aecbf6/bzImage-88690811.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P3577/1:b..l
(detected by 1, t=10503 jiffies, g=18013, q=67 ncpus=2)
task:syz-executor.4 state:R running task stack:19864 pid:3577 ppid:3571 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
preempt_schedule_irq+0xf7/0x1c0 kernel/sched/core.c:6870
irqentry_exit+0x53/0x80 kernel/entry/common.c:439
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:__rcu_read_lock+0x4c/0xb0 kernel/rcu/tree_plugin.h:404
Code: 48 c1 eb 03 42 0f b6 04 33 84 c0 75 2f 41 8b 2f ff c5 42 0f b6 04 33 84 c0 75 38 41 89 2f 42 0f b6 04 33 84 c0 75 43 41 8b 07 <3d> 00 00 00 40 7d 07 5b 41 5e 41 5f 5d c3 0f 0b eb f5 44 89 f9 80
RSP: 0018:ffffc900040af780 EFLAGS: 00000246
RAX: 0000000000000001 RBX: 1ffff11003ddd7f7 RCX: ffff88801eeebb80
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 00007fda52c7bdda
RBP: 0000000000000001 R08: ffffffff817688e0 R09: ffffc900040af930
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88801eeebb80
R13: ffffffff81784820 R14: dffffc0000000000 R15: ffff88801eeebfbc
rcu_read_lock include/linux/rcupdate.h:789 [inline]
is_bpf_text_address+0x1b/0x2a0 kernel/bpf/core.c:731
kernel_text_address+0x9f/0xd0 kernel/extable.c:125
__kernel_text_address+0x9/0x40 kernel/extable.c:79
unwind_get_return_address+0x49/0x80 arch/x86/kernel/unwind_orc.c:323
arch_stack_walk+0xf3/0x140 arch/x86/kernel/stacktrace.c:26
stack_trace_save+0x113/0x1c0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:52
kasan_save_free_info+0x27/0x40 mm/kasan/generic.c:516
____kasan_slab_free+0xd6/0x120 mm/kasan/common.c:236
kasan_slab_free include/linux/kasan.h:177 [inline]
slab_free_hook mm/slub.c:1724 [inline]
slab_free_freelist_hook mm/slub.c:1750 [inline]
slab_free mm/slub.c:3661 [inline]
kmem_cache_free+0x292/0x510 mm/slub.c:3683
__dentry_kill+0x4f4/0x650 fs/dcache.c:621
dentry_kill+0xbb/0x290
dput+0xfb/0x1d0 fs/dcache.c:914
__fput+0x5e4/0x890 fs/file_table.c:328
task_work_run+0x246/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xde/0x100 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:303
do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fda52c7bdda
RSP: 002b:00007ffe7491e910 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000003 RCX: 00007fda52c7bdda
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 00007ffe7491e98c R08: 00007ffe7491e28c R09: 00007ffe7491e677
R10: 00007ffe7491e2e0 R11: 0000000000000293 R12: 0000000000000032
R13: 0000000000021fa2 R14: 0000000000021579 R15: 0000000000000015
</TASK>
rcu: rcu_preempt kthread starved for 10546 jiffies! g18013 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:26240 pid:16 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1965
rcu_gp_fqs_loop+0x2d2/0x1150 kernel/rcu/tree.c:1706
rcu_gp_kthread+0xa3/0x3b0 kernel/rcu/tree.c:1905
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4953 Comm: syz-executor.1 Not tainted 6.1.92-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:jhash2 include/linux/jhash.h:128 [inline]
RIP: 0010:futex_hash kernel/futex/core.c:117 [inline]
RIP: 0010:futex_q_lock+0x86/0x230 kernel/futex/core.c:528
Code: 48 89 f8 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 66 01 00 00 41 8b 5f 3c 01 eb 49 8d 7f 40 48 89 f8 48 c1 e8 03 42 0f b6 04 20 <84> c0 0f 85 62 01 00 00 41 03 6f 40 41 29 ee 89 e8 c1 c0 04 44 31
RSP: 0018:ffffc9000341fa30 EFLAGS: 00000a02
RAX: 0000000000000000 RBX: 00000000dead47d7 RCX: 0000000000040000
RDX: ffffc9000a59c000 RSI: 000000000003ffff RDI: ffffc9000341fc90
RBP: 00000000deadbf57 R08: ffffffff817ed7cf R09: fffff52000683f98
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffffc9000341fc30 R14: 0000000007674e57 R15: ffffc9000341fc50
FS: 00007f71f58b26c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b33031000 CR3: 000000007db48000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
futex_wait_setup+0x106/0x340 kernel/futex/waitwake.c:607
futex_wait+0x1b5/0x5c0 kernel/futex/waitwake.c:651
do_futex+0x3b5/0x490 kernel/futex/syscalls.c:106
__do_sys_futex kernel/futex/syscalls.c:183 [inline]
__se_sys_futex+0x3d7/0x460 kernel/futex/syscalls.c:164
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f71f4a7cee9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f71f58b2178 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007f71f4bb4058 RCX: 00007f71f4a7cee9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007f71f4bb4058
RBP: 00007f71f4bb4050 R08: 00007f71f58b26c0 R09: 00007f71f58b26c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f71f4bb405c
R13: 000000000000006e R14: 00007fffd5d6b990 R15: 00007fffd5d6ba78
</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