[Android 5.15] BUG: scheduling while atomic in tracepoint_probe_register_prio_may_exist

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 993bed180178 Merge "Merge branch 'android13-5.15' into bra..
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=16d34f1a180000
kernel config: https://syzkaller.appspot.com/x/.config?x=49ce29477ba81e8f
dashboard link: https://syzkaller.appspot.com/bug?extid=ab599f98e6255ad500e4
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=16903c4a180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d00be8180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4098d24d4c8b/disk-993bed18.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/94fbc07ac02d/vmlinux-993bed18.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eed14de06c19/bzImage-993bed18.xz

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

BUG: scheduling while atomic: syz-executor210/348/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff81c22229>] rcu_read_lock_sched include/linux/rcupdate.h:786 [inline]
[<ffffffff81c22229>] fd_install+0x59/0x250 fs/file.c:607
CPU: 1 PID: 348 Comm: syz-executor210 Not tainted 5.15.148-syzkaller-00718-g993bed180178 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
dump_stack+0x15/0x17 lib/dump_stack.c:113
__schedule_bug+0x195/0x260 kernel/sched/core.c:5707
schedule_debug kernel/sched/core.c:5734 [inline]
__schedule+0xd19/0x1590 kernel/sched/core.c:6402
schedule+0x11f/0x1e0 kernel/sched/core.c:6595
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6654
mutex_optimistic_spin kernel/locking/mutex.c:521 [inline]
__mutex_lock_common kernel/locking/mutex.c:620 [inline]
__mutex_lock+0x5b5/0x1870 kernel/locking/mutex.c:755
__mutex_lock_slowpath+0xe/0x10 kernel/locking/mutex.c:1006
mutex_lock+0x135/0x1e0 kernel/locking/mutex.c:288
tracepoint_probe_register_prio_may_exist+0xb5/0x180 kernel/tracepoint.c:478
tracepoint_probe_register_may_exist include/linux/tracepoint.h:52 [inline]
__bpf_probe_register kernel/trace/bpf_trace.c:1946 [inline]
bpf_probe_register+0x152/0x1e0 kernel/trace/bpf_trace.c:1952
bpf_raw_tracepoint_open+0x610/0x950 kernel/bpf/syscall.c:3087
__sys_bpf+0x489/0x760 kernel/bpf/syscall.c:4669
__do_sys_bpf kernel/bpf/syscall.c:4731 [inline]
__se_sys_bpf kernel/bpf/syscall.c:4729 [inline]
__x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:4729
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7ff998496ee9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 17 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:00007ffeaca9bf58 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ff998496ee9
RDX: 0000000000000010 RSI: 0000000020000040 RDI: 0000000000000011
RBP: 0000000000000000 R08: 00000000000000a0 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</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 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