[v6.1] INFO: rcu detected stall in security_file_ioctl

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8b4118fabd6e Linux 6.1.78
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=105d61e8180000
kernel config: https://syzkaller.appspot.com/x/.config?x=93bcaf862378a9b8
dashboard link: https://syzkaller.appspot.com/bug?extid=0e21429a9aacc1a8de3f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14d26ffc180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1637fd58180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f5708019df51/disk-8b4118fa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/646777c7d071/vmlinux-8b4118fa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/603070686d6f/bzImage-8b4118fa.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 1-...0: (1 GPs behind) idle=91ec/1/0x4000000000000000 softirq=7279/7280 fqs=5250
(detected by 0, t=10502 jiffies, g=6405, q=419 ncpus=2)
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 3571 Comm: syz-executor331 Not tainted 6.1.78-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
RIP: 0010:hlock_class kernel/locking/lockdep.c:223 [inline]
RIP: 0010:mark_lock+0x68/0x340 kernel/locking/lockdep.c:4606
Code: f6 43 02 03 40 0f 94 c5 83 f5 09 eb 0b 89 d5 83 fa 20 0f 83 d2 02 00 00 41 be 01 00 00 00 89 e9 41 d3 e6 49 8d 5f 20 48 89 d8 <48> c1 e8 03 42 0f b6 04 28 84 c0 0f 85 29 02 00 00 8b 1b 81 e3 ff
RSP: 0018:ffffc900001e0a18 EFLAGS: 00000083
RAX: ffff88807efae468 RBX: ffff88807efae468 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff88807efae448 RDI: ffff88807efad940
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffffbfff2092260
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807efae418
R13: dffffc0000000000 R14: 0000000000000001 R15: ffff88807efae448
FS: 0000555555c9c380(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000078246000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
mark_usage kernel/locking/lockdep.c:4520 [inline]
__lock_acquire+0xb40/0x1f80 kernel/locking/lockdep.c:5003
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:350 [inline]
advance_sched+0x47/0x970 net/sched/sch_taprio.c:700
__run_hrtimer kernel/time/hrtimer.c:1686 [inline]
__hrtimer_run_queues+0x5e5/0xe50 kernel/time/hrtimer.c:1750
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1812
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:tomoyo_check_acl+0xae/0x3e0 security/tomoyo/domain.c:173
Code: 03 42 0f b6 04 28 84 c0 0f 85 bd 02 00 00 4d 8b 37 4d 39 fe 0f 84 e5 01 00 00 49 8d 6e 18 48 89 e8 48 c1 e8 03 42 0f b6 04 28 <84> c0 0f 85 09 01 00 00 0f b6 6d 00 31 ff 89 ee e8 8d 68 98 fd 85
RSP: 0018:ffffc90003c4fba0 EFLAGS: 00000a06
RAX: 0000000000000000 RBX: 0000000000000004 RCX: ffff88807efad940
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000004
RBP: ffff88801354d318 R08: ffffffff83f217c6 R09: ffffffff83f3aed8
R10: 0000000000000002 R11: ffff88807efad940 R12: 0000000000000000
R13: dffffc0000000000 R14: ffff88801354d300 R15: ffff888022ae2b90
tomoyo_path_number_perm+0x430/0x7f0 security/tomoyo/file.c:733
security_file_ioctl+0x6d/0xa0 security/security.c:1568
__do_sys_ioctl fs/ioctl.c:864 [inline]
__se_sys_ioctl+0x47/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f96566f40a9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 d1 19 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd16154788 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f96566f40a9
RDX: 0000000000000000 RSI: 0000000000008933 RDI: 0000000000000006
RBP: 0000000000000000 R08: 0000000100000000 R09: 0000000100000000
R10: 0000000100000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.707 msecs


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