[Android 5.15] BUG: scheduling while atomic in trace_set_clr_event

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3802b45594e1 Revert "clk: fixed-rate: add devm_clk_hw_regi..
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=1429581c180000
kernel config: https://syzkaller.appspot.com/x/.config?x=71b415a99493d134
dashboard link: https://syzkaller.appspot.com/bug?extid=f86125c57114fccdaa69
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=17f24410180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12900f92180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/dd4d3bdb87f1/disk-3802b455.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a6dd15e230e4/vmlinux-3802b455.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ca3496f788a9/bzImage-3802b455.xz

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

BUG: scheduling while atomic: syz-executor765/2807/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff81ab6d7d>] spin_lock include/linux/spinlock.h:363 [inline]
[<ffffffff81ab6d7d>] preload_this_cpu_lock mm/vmalloc.c:1511 [inline]
[<ffffffff81ab6d7d>] alloc_vmap_area+0x22d/0x1a80 mm/vmalloc.c:1553
CPU: 1 PID: 2807 Comm: syz-executor765 Not tainted 5.15.148-syzkaller-00704-g3802b45594e1 #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+0xd0b/0x1580 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
__ftrace_set_clr_event kernel/trace/trace_events.c:1050 [inline]
trace_set_clr_event+0xcb/0x140 kernel/trace/trace_events.c:1116
bpf_get_trace_printk_proto+0x22/0x80 kernel/trace/bpf_trace.c:411
bpf_tracing_func_proto+0xb4/0x4a0 kernel/trace/bpf_trace.c:1073
raw_tp_prog_func_proto+0x67/0x80 kernel/trace/bpf_trace.c:1520
check_helper_call+0x1bf/0x6000 kernel/bpf/verifier.c:6467
do_check+0x8476/0xf2c0 kernel/bpf/verifier.c:11338
do_check_common+0x909/0x1290 kernel/bpf/verifier.c:13408
do_check_main kernel/bpf/verifier.c:13471 [inline]
bpf_check+0x3835/0x12bf0 kernel/bpf/verifier.c:14042
bpf_prog_load+0x12ac/0x1b50 kernel/bpf/syscall.c:2327
__sys_bpf+0x4bc/0x760 kernel/bpf/syscall.c:4627
__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:0x7f1e0cac48d9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 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:00007f1e0ca85228 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007f1e0cb4f328 RCX: 00007f1e0cac48d9
RDX: 0000000000000049 RSI: 0000000020000980 RDI: 0000000000000005
RBP: 00007f1e0cb4f320 R08: 00007ffc1f6e9707 R09: 00007f1e0ca856c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f1e0cb1bf7c
R13: 00007f1e0cb1b078 R14: 0000000020001940 R15: 00007ffc1f6e9708
</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