[syzbot] [kernel?] linux-next test error: WARNING in tmigr_cpu_prepare

[syzbot <syzbot+198e5d62f814bce1e600@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    2347b4c79f5e Add linux-next specific files for 20240723
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10d8ad3d980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=befe10ad51f9f2bb
dashboard link: https://syzkaller.appspot.com/bug?extid=198e5d62f814bce1e600
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9ccc2b0cb372/disk-2347b4c7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/469c95cf67be/vmlinux-2347b4c7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/25b4013add8e/bzImage-2347b4c7.xz

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

smpboot: CPU0: Intel(R) Xeon(R) CPU @ 2.20GHz (family: 0x6, model: 0x4f, stepping: 0x0)
Running RCU Tasks wait API self tests
Running RCU Tasks Trace wait API self tests
Performance Events: unsupported p6 CPU model 79 no PMU driver, software events only.
signal: max sigframe size: 1776
rcu: Hierarchical SRCU implementation.
rcu: 	Max phase no-delay instances is 1000.
Timer migration: 1 hierarchy levels; 8 children per group; 0 crossnode level
------------[ cut here ]------------
WARNING: CPU: 0 PID: 1 at kernel/time/timer_migration.c:1714 tmigr_cpu_prepare+0x10e4/0x1330 kernel/time/timer_migration.c:1714
Modules linked in:
CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.10.0-next-20240723-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
RIP: 0010:tmigr_cpu_prepare+0x10e4/0x1330 kernel/time/timer_migration.c:1714
Code: 0d 00 e9 41 fe ff ff e8 ea d3 0d 00 e9 37 fe ff ff 80 3d 81 ea 13 0e 01 75 26 e8 d7 d3 0d 00 e9 24 fe ff ff e8 cd d3 0d 00 90 <0f> 0b 90 e9 a8 ef ff ff e8 bf d3 0d 00 90 0f 0b 90 e9 6e ff ff ff
RSP: 0000:ffffc900000676f0 EFLAGS: 00010293
RAX: ffffffff8185f723 RBX: 0000000000000000 RCX: ffff8880172a8000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff8880b942d2a0 R08: ffffffff8185e6c6 R09: 1ffffffff1f5f34d
R10: dffffc0000000000 R11: ffffffff8185e640 R12: dffffc0000000000
R13: 0000000000000040 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88823ffff000 CR3: 000000000e134000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 cpuhp_invoke_callback+0x48d/0x830 kernel/cpu.c:194
 cpuhp_issue_call+0x46f/0x7e0
 __cpuhp_setup_state_cpuslocked+0x464/0x730 kernel/cpu.c:2505
 __cpuhp_setup_state+0x3f/0x60 kernel/cpu.c:2534
 cpuhp_setup_state include/linux/cpuhotplug.h:277 [inline]
 tmigr_init+0x231/0x2a0 kernel/time/timer_migration.c:1794
 do_one_initcall+0x248/0x880 init/main.c:1267
 do_pre_smp_initcalls+0x57/0xa0 init/main.c:1373
 kernel_init_freeable+0x40d/0x5d0 init/main.c:1567
 kernel_init+0x1d/0x2b0 init/main.c:1467
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:144
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </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 syzkaller@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 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