[moderation] [kernel?] KCSAN: data-race in __tmigr_cpu_deactivate / tmigr_handle_remote

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 82affc97affb Revert "KVM: arm64: Snapshot all non-zero RES..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1710c2a5180000
kernel config: https://syzkaller.appspot.com/x/.config?x=f6807a59ab85347d
dashboard link: https://syzkaller.appspot.com/bug?extid=9573fbf76e97a4b394fa
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [jst...@google.com linux-...@vger.kernel.org sb...@kernel.org tg...@linutronix.de]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/175584fda655/disk-82affc97.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b8a602810acd/vmlinux-82affc97.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a721d869e368/bzImage-82affc97.xz

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

==================================================================
BUG: KCSAN: data-race in __tmigr_cpu_deactivate / tmigr_handle_remote

write to 0xffff888237d20624 of 1 bytes by task 0 on cpu 1:
__tmigr_cpu_deactivate+0x83/0x470 kernel/time/timer_migration.c:1335
tmigr_cpu_deactivate+0x66/0x180 kernel/time/timer_migration.c:1361
timer_use_tmigr kernel/time/timer.c:2192 [inline]
__get_next_timer_interrupt+0x137/0x530 kernel/time/timer.c:2267
timer_base_try_to_set_idle+0x54/0x60 kernel/time/timer.c:2349
tick_nohz_stop_tick kernel/time/tick-sched.c:981 [inline]
tick_nohz_idle_stop_tick+0x15b/0x640 kernel/time/tick-sched.c:1217
cpuidle_idle_call kernel/sched/idle.c:232 [inline]
do_idle+0x178/0x230 kernel/sched/idle.c:332
cpu_startup_entry+0x25/0x30 kernel/sched/idle.c:430
start_secondary+0x94/0xa0 arch/x86/kernel/smpboot.c:313
common_startup_64+0x12c/0x137

read to 0xffff888237d20624 of 1 bytes by interrupt on cpu 0:
tmigr_next_groupevt kernel/time/timer_migration.c:569 [inline]
tmigr_next_expired_groupevt kernel/time/timer_migration.c:593 [inline]
tmigr_handle_remote_up kernel/time/timer_migration.c:1013 [inline]
__walk_groups kernel/time/timer_migration.c:488 [inline]
tmigr_handle_remote+0x23f/0x8e0 kernel/time/timer_migration.c:1074
run_timer_softirq+0x5f/0x70 kernel/time/timer.c:2442
__do_softirq+0xc8/0x285 kernel/softirq.c:554
invoke_softirq kernel/softirq.c:428 [inline]
__irq_exit_rcu kernel/softirq.c:633 [inline]
irq_exit_rcu+0x3c/0x90 kernel/softirq.c:645
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline]
sysvec_apic_timer_interrupt+0x73/0x80 arch/x86/kernel/apic/apic.c:1043
asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702
native_safe_halt arch/x86/include/asm/irqflags.h:48 [inline]
arch_safe_halt arch/x86/include/asm/irqflags.h:86 [inline]
acpi_safe_halt+0x21/0x30 drivers/acpi/processor_idle.c:112
acpi_idle_do_entry+0x1d/0x30 drivers/acpi/processor_idle.c:573
acpi_idle_enter+0x96/0xb0 drivers/acpi/processor_idle.c:707
cpuidle_enter_state+0xcf/0x270 drivers/cpuidle/cpuidle.c:267
cpuidle_enter+0x40/0x70 drivers/cpuidle/cpuidle.c:388
call_cpuidle kernel/sched/idle.c:155 [inline]
cpuidle_idle_call kernel/sched/idle.c:236 [inline]
do_idle+0x195/0x230 kernel/sched/idle.c:332
cpu_startup_entry+0x25/0x30 kernel/sched/idle.c:430
rest_init+0xef/0xf0 init/main.c:732
start_kernel+0x57c/0x5e0 init/main.c:1074
x86_64_start_reservations+0x2a/0x30 arch/x86/kernel/head64.c:509
x86_64_start_kernel+0x94/0xa0 arch/x86/kernel/head64.c:490
common_startup_64+0x12c/0x137

value changed: 0x01 -> 0x00

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.8.0-syzkaller-11064-g82affc97affb #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
==================================================================


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