[moderation] [kernel?] KCSAN: data-race in tick_nohz_highres_handler / tick_nohz_idle_stop_tick (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 54be6c6c5ae8 Linux 6.8-rc3
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13160a9fe80000
kernel config: https://syzkaller.appspot.com/x/.config?x=3cd0dc1b46a5bc5c
dashboard link: https://syzkaller.appspot.com/bug?extid=c00a921107c2e486ef05
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [fred...@kernel.org linux-...@vger.kernel.org mi...@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/148fa7492b49/disk-54be6c6c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cfb5e0d97c64/vmlinux-54be6c6c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4eff3a827e09/bzImage-54be6c6c.xz

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

==================================================================
BUG: KCSAN: data-race in tick_nohz_highres_handler / tick_nohz_idle_stop_tick

write to 0xffffffff8611ecb0 of 4 bytes by task 0 on cpu 0:
tick_nohz_stop_tick kernel/time/tick-sched.c:907 [inline]
tick_nohz_idle_stop_tick+0x1d8/0x760 kernel/time/tick-sched.c:1133
cpuidle_idle_call kernel/sched/idle.c:211 [inline]
do_idle+0x177/0x230 kernel/sched/idle.c:312
cpu_startup_entry+0x24/0x30 kernel/sched/idle.c:410
rest_init+0xf3/0x100 init/main.c:730
arch_call_rest_init+0x9/0x10 init/main.c:827
start_kernel+0x57d/0x5e0 init/main.c:1072
x86_64_start_reservations+0x2a/0x30 arch/x86/kernel/head64.c:555
x86_64_start_kernel+0x94/0xa0 arch/x86/kernel/head64.c:536
secondary_startup_64_no_verify+0x15f/0x16b

read to 0xffffffff8611ecb0 of 4 bytes by interrupt on cpu 1:
tick_sched_do_timer kernel/time/tick-sched.c:201 [inline]
tick_nohz_highres_handler+0x3d/0x2c0 kernel/time/tick-sched.c:1512
__run_hrtimer kernel/time/hrtimer.c:1688 [inline]
__hrtimer_run_queues+0x217/0x710 kernel/time/hrtimer.c:1752
hrtimer_interrupt+0x20d/0x7b0 kernel/time/hrtimer.c:1814
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1065 [inline]
__sysvec_apic_timer_interrupt+0x52/0x190 arch/x86/kernel/apic/apic.c:1082
sysvec_apic_timer_interrupt+0x6a/0x80 arch/x86/kernel/apic/apic.c:1076
asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:649
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+0x20/0x30 drivers/acpi/processor_idle.c:112
acpi_idle_do_entry+0x19/0x30 drivers/acpi/processor_idle.c:573
acpi_idle_enter+0x96/0xb0 drivers/acpi/processor_idle.c:707
cpuidle_enter_state+0xd1/0x270 drivers/cpuidle/cpuidle.c:267
cpuidle_enter+0x40/0x60 drivers/cpuidle/cpuidle.c:388
call_cpuidle kernel/sched/idle.c:134 [inline]
cpuidle_idle_call kernel/sched/idle.c:215 [inline]
do_idle+0x194/0x230 kernel/sched/idle.c:312
cpu_startup_entry+0x24/0x30 kernel/sched/idle.c:410
start_secondary+0x82/0x90 arch/x86/kernel/smpboot.c:336
secondary_startup_64_no_verify+0x15f/0x16b

value changed: 0x00000000 -> 0xffffffff

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.8.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.