[v5.15] BUG: sleeping function called from invalid context in bpf_prog_alloc_no_stats

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6139f2a02fe0 Linux 5.15.148
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14997df0180000
kernel config: https://syzkaller.appspot.com/x/.config?x=c170eb20d8be8542
dashboard link: https://syzkaller.appspot.com/bug?extid=d81da6ebba545c771dbf
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=1210a09c180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17efaae8180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2ac68f24aed3/disk-6139f2a0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e8982a3768c5/vmlinux-6139f2a0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eb272dd019ce/bzImage-6139f2a0.xz

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

BUG: sleeping function called from invalid context at include/linux/sched/mm.h:209
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 9534, name: syz-executor200
no locks held by syz-executor200/9534.
Preemption disabled at:
[<0000000000000000>] 0x0
CPU: 1 PID: 9534 Comm: syz-executor200 Not tainted 5.15.148-syzkaller #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+0x1e3/0x2cb lib/dump_stack.c:106
___might_sleep+0x547/0x6a0 kernel/sched/core.c:9626
might_alloc include/linux/sched/mm.h:209 [inline]
slab_pre_alloc_hook+0x44/0xc0 mm/slab.h:492
slab_alloc_node mm/slub.c:3134 [inline]
__kmalloc_node+0x71/0x390 mm/slub.c:4451
kmalloc_node include/linux/slab.h:614 [inline]
__vmalloc_area_node mm/vmalloc.c:2910 [inline]
__vmalloc_node_range+0x2e2/0x8c0 mm/vmalloc.c:3029
__vmalloc_node mm/vmalloc.c:3079 [inline]
__vmalloc+0x75/0x80 mm/vmalloc.c:3093
bpf_prog_alloc_no_stats+0x33/0x2f0 kernel/bpf/core.c:90
bpf_prog_alloc+0x18/0x1d0 kernel/bpf/core.c:124
bpf_prog_load+0x800/0x1b60 kernel/bpf/syscall.c:2272
__sys_bpf+0x343/0x670 kernel/bpf/syscall.c:4623
__do_sys_bpf kernel/bpf/syscall.c:4727 [inline]
__se_sys_bpf kernel/bpf/syscall.c:4725 [inline]
__x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:4725
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:0x7f480c5acee9
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:00007ffec852e8c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f480c5acee9
RDX: 0000000000000049 RSI: 0000000020000980 RDI: 0000000000000005
RBP: 00000000000f4240 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000024c43
R13: 00007ffec852e8dc R14: 00007ffec852e8f0 R15: 00007ffec852e8e0
</TASK>
BUG: scheduling while atomic: syz-executor200/9534/0x00000002
no locks held by syz-executor200/9534.
Modules linked in:
Preemption disabled at:
[<0000000000000000>] 0x0


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

[syzbot]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.