[Android 6.1] BUG: scheduling while atomic in synchronize_rcu_expedited

Hello,

syzbot found the following issue on:

HEAD commit: bd552fcbbd0f ANDROID: GKI: Update rockchip symbols to add ..
git tree: android14-6.1
console output: https://syzkaller.appspot.com/x/log.txt?x=14758ddc980000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a340f281ebc7608
dashboard link: https://syzkaller.appspot.com/bug?extid=7aae5c996031cff11107
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=156f18ec980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167b8bd0980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6b23dd421362/disk-bd552fcb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e6d25d4e05a0/vmlinux-bd552fcb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cfb2a8c9439f/bzImage-bd552fcb.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

BUG: scheduling while atomic: syz-executor412/701/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff82a01b5d>] ref_tracker_free+0x11d/0x7d0 lib/ref_tracker.c:124
CPU: 0 PID: 701 Comm: syz-executor412 Not tainted 6.1.75-syzkaller-00021-gbd552fcbbd0f #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:5964
schedule_debug kernel/sched/core.c:5991 [inline]
__schedule+0xcf7/0x1550 kernel/sched/core.c:6626
schedule+0xc3/0x180 kernel/sched/core.c:6809
synchronize_rcu_expedited+0x6fc/0x890 kernel/rcu/tree_exp.h:965
synchronize_net net/core/dev.c:10787 [inline]
unregister_netdevice_many+0x1378/0x1740 net/core/dev.c:10919
unregister_netdevice_queue+0x2e6/0x350 net/core/dev.c:10816
unregister_netdevice include/linux/netdevice.h:3100 [inline]
ppp_release+0xed/0x1e0 drivers/net/ppp/ppp_generic.c:407
__fput+0x3ab/0x870 fs/file_table.c:320
____fput+0x15/0x20 fs/file_table.c:348
task_work_run+0x24d/0x2e0 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0x94/0xa0 kernel/entry/common.c:171
exit_to_user_mode_prepare+0x5a/0xa0 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x26/0x140 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fca2bec0be0
Code: ff f7 d8 64 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 80 3d c1 94 07 00 00 74 17 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c
RSP: 002b:00007ffdbc3198e8 EFLAGS: 00000202 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000007 RCX: 00007fca2bec0be0
RDX: 0000000000000010 RSI: 00000000200001c0 RDI: 0000000000000006
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 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 [email protected].

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

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