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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ee5e09825b81 Linux 6.1.106
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12ef6243980000
kernel config: https://syzkaller.appspot.com/x/.config?x=18dcbe43e0e5806e
dashboard link: https://syzkaller.appspot.com/bug?extid=c8137155968acf081db3
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/5fb3bf93c3b1/disk-ee5e0982.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ef8ac982339a/vmlinux-ee5e0982.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c96f887afa9f/bzImage-ee5e0982.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P3091/2:b..l
(detected by 0, t=10502 jiffies, g=77105, q=205 ncpus=2)
task:udevd state:R running task stack:22600 pid:3091 ppid:1 flags:0x00004002
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 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:lock_acquire+0x26f/0x5a0 kernel/locking/lockdep.c:5666
Code: 2b 00 74 08 4c 89 f7 e8 3f aa 77 00 f6 44 24 61 02 0f 85 84 01 00 00 41 f7 c7 00 02 00 00 74 01 fb 48 c7 44 24 40 0e 36 e0 45 <4b> c7 44 25 00 00 00 00 00 43 c7 44 25 09 00 00 00 00 43 c7 44 25
RSP: 0018:ffffc9000319f260 EFLAGS: 00000206
RAX: 0000000000000001 RBX: 1ffff92000633e58 RCX: 1ffff92000633df8
RDX: dffffc0000000000 RSI: ffffffff8b0c13e0 RDI: ffffffff8b5d62c0
RBP: ffffc9000319f3a8 R08: dffffc0000000000 R09: fffffbfff20e7645
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92000633e54
R13: dffffc0000000000 R14: ffffc9000319f2c0 R15: 0000000000000246
rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
rcu_read_lock include/linux/rcupdate.h:791 [inline]
prepend_path+0x1f0/0xbe0 fs/d_path.c:167
d_absolute_path+0x175/0x300 fs/d_path.c:233
tomoyo_get_absolute_path security/tomoyo/realpath.c:101 [inline]
tomoyo_realpath_from_path+0x2aa/0x5d0 security/tomoyo/realpath.c:271
tomoyo_get_realpath security/tomoyo/file.c:151 [inline]
tomoyo_check_open_permission+0x240/0x4c0 security/tomoyo/file.c:771
security_file_open+0x5f/0xa0 security/security.c:1681
do_dentry_open+0x308/0x10f0 fs/open.c:869
do_open fs/namei.c:3628 [inline]
path_openat+0x2644/0x2e60 fs/namei.c:3785
do_filp_open+0x230/0x480 fs/namei.c:3812
do_sys_openat2+0x13b/0x4f0 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1345
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:0x7f0a6cd6f477
RSP: 002b:00007fff0e6068e8 EFLAGS: 00000287 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 000055fb077902c0 RCX: 00007f0a6cd6f477
RDX: 0000000000090800 RSI: 000055fb077973a0 RDI: 00000000ffffff9c
RBP: 000055fb077d0990 R08: 0000000000090800 R09: 000055fb077973a0
R10: 0000000000000000 R11: 0000000000000287 R12: 000055fb077973a0
R13: 00000000000000ff R14: 000055fb06a511c4 R15: 0000000000000000
</TASK>
rcu: rcu_preempt kthread starved for 10340 jiffies! g77105 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
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:25368 pid:16 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 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:295
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 1 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_safe_halt drivers/acpi/processor_idle.c:111 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:567


---
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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.