[Android 6.1] BUG: scheduling while atomic in bpf_prog_pack_alloc

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: af361f9a1066 UPSTREAM: usb: typec: Return size of buffer i..
git tree: android14-6.1
console output: https://syzkaller.appspot.com/x/log.txt?x=168ceaf6180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7bd1a415c6de5d9d
dashboard link: https://syzkaller.appspot.com/bug?extid=bcbfe1cabfaec75ad55a
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=12b9433d180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=168a2415180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3c879fc08bf7/disk-af361f9a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1254d9d7bde4/vmlinux-af361f9a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/764708030362/bzImage-af361f9a.xz

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

BUG: scheduling while atomic: syz-executor283/301/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8163d72f>] is_module_text_address+0x1f/0x360 kernel/module/main.c:3140
CPU: 1 PID: 301 Comm: syz-executor283 Not tainted 6.1.75-syzkaller-00112-gaf361f9a1066 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/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/0x1b lib/dump_stack.c:113
__schedule_bug+0x195/0x260 kernel/sched/core.c:5960
schedule_debug kernel/sched/core.c:5987 [inline]
__schedule+0xcf7/0x1550 kernel/sched/core.c:6622
schedule+0xc3/0x180 kernel/sched/core.c:6805
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6864
mutex_optimistic_spin kernel/locking/mutex.c:529 [inline]
__mutex_lock_common kernel/locking/mutex.c:629 [inline]
__mutex_lock+0x5b6/0x1ca0 kernel/locking/mutex.c:774
__mutex_lock_slowpath+0xe/0x10 kernel/locking/mutex.c:1063
mutex_lock+0x130/0x1e0 kernel/locking/mutex.c:295
bpf_prog_pack_alloc+0x2b/0x380 kernel/bpf/core.c:884
bpf_jit_binary_pack_alloc+0x1ab/0x540 kernel/bpf/core.c:1082
bpf_int_jit_compile+0xb4aa/0xca30 arch/x86/net/bpf_jit_comp.c:2440
bpf_prog_select_runtime+0x8da/0xc10 kernel/bpf/core.c:2191
bpf_prog_load+0x136d/0x1bf0 kernel/bpf/syscall.c:2609
__sys_bpf+0x52c/0x7f0 kernel/bpf/syscall.c:4981
__do_sys_bpf kernel/bpf/syscall.c:5085 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5083 [inline]
__x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5083
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:0x7f864e8f7ee9
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:00007ffebec97e78 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f864e8f7ee9
RDX: 0000000000000048 RSI: 0000000020000b40 RDI: 0000000000000005
RBP: 00000000000f4240 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000004cef
R13: 00007ffebec97e8c R14: 00007ffebec97ea0 R15: 00007ffebec97e90
</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