[Android 6.1] BUG: scheduling while atomic in bpf_dispatcher_change_prog

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4c25eb8ea5a2 ANDROID: EXPORT raise_softirq and update the ..
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=113d69d1180000
kernel config: https://syzkaller.appspot.com/x/.config?x=54c503ca94c7e582
dashboard link: https://syzkaller.appspot.com/bug?extid=61fde469491b889594e3
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=14a2a6fa180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=139ee5c1180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f40a4289bb92/disk-4c25eb8e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8318270d162f/vmlinux-4c25eb8e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2731726cc364/bzImage-4c25eb8e.xz

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

BUG: scheduling while atomic: syz-executor210/319/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff818eaf88>] try_get_fmt_tmp_buf kernel/bpf/helpers.c:768 [inline]
[<ffffffff818eaf88>] bpf_bprintf_prepare+0x118/0x1360 kernel/bpf/helpers.c:818
CPU: 1 PID: 319 Comm: syz-executor210 Not tainted 6.1.68-syzkaller-00058-g4c25eb8ea5a2 #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/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_dispatcher_change_prog+0xa0/0xf20 kernel/bpf/dispatcher.c:141
bpf_prog_change_xdp+0x24/0x30 net/core/filter.c:11462
bpf_prog_test_run_xdp+0x97a/0x1130 net/bpf/test_run.c:1407
bpf_prog_test_run+0x3b0/0x630 kernel/bpf/syscall.c:3635
__sys_bpf+0x59f/0x7f0 kernel/bpf/syscall.c:4990
__do_sys_bpf kernel/bpf/syscall.c:5076 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5074 [inline]
__x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5074
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:0x7f8d909b6fe9
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:00007ffecaf17c98 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f8d909b6fe9
RDX: 0000000000000050 RSI: 0000000020000640 RDI: 000000000000000a
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