[Android 6.1] BUG: scheduling while atomic in rcu_boost_kthread

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 92432f07d663 ANDROID: GKI: Update the ABI symbol list
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=16a7722c180000
kernel config: https://syzkaller.appspot.com/x/.config?x=54c503ca94c7e582
dashboard link: https://syzkaller.appspot.com/bug?extid=f6ea0dae9bc786f577f7
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=117995d0180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d23152180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/59b1cbc5a010/disk-92432f07.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9cb1d1ff7b1e/vmlinux-92432f07.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eadaf55bbae8/bzImage-92432f07.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/9fc5c37b0207/mount_0.gz

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

BUG: scheduling while atomic: rcub/0/15/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff84fe3947>] rt_mutex_slowlock_block+0xf7/0x5a0 kernel/locking/rtmutex.c:1574
CPU: 0 PID: 15 Comm: rcub/0 Not tainted 6.1.68-syzkaller-00023-g92432f07d663 #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+0xce9/0x1540 kernel/sched/core.c:6622
schedule+0xc3/0x180 kernel/sched/core.c:6805
rcu_boost_kthread+0x11f/0x6e0 kernel/rcu/tree_plugin.h:1120
kthread+0x26d/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</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