KCSAN: data-race in tick_nohz_stop_tick / tick_sched_timer (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0477e928 Linux 5.10-rc7
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11769745500000
kernel config: https://syzkaller.appspot.com/x/.config?x=329e76890d0bf5c3
dashboard link: https://syzkaller.appspot.com/bug?extid=ae4c889bc7d1304cc450
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project.git 913f6005669cfb590c99865a90bc51ed0983d09d)
CC: [fwei...@gmail.com linux-...@vger.kernel.org mi...@kernel.org tg...@linutronix.de]

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

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

==================================================================
BUG: KCSAN: data-race in tick_nohz_stop_tick / tick_sched_timer

write to 0xffffffff86fc1ad0 of 4 bytes by interrupt on cpu 0:
tick_sched_do_timer kernel/time/tick-sched.c:141 [inline]
tick_sched_timer+0x1f5/0x210 kernel/time/tick-sched.c:1321
__run_hrtimer+0x133/0x420 kernel/time/hrtimer.c:1519
__hrtimer_run_queues kernel/time/hrtimer.c:1583 [inline]
hrtimer_interrupt+0x36e/0xa10 kernel/time/hrtimer.c:1645
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1080 [inline]
__sysvec_apic_timer_interrupt+0x6f/0x200 arch/x86/kernel/apic/apic.c:1097
asm_call_irq_on_stack+0xf/0x20
__run_sysvec_on_irqstack arch/x86/include/asm/irq_stack.h:37 [inline]
run_sysvec_on_irqstack_cond arch/x86/include/asm/irq_stack.h:89 [inline]
sysvec_apic_timer_interrupt+0x52/0x90 arch/x86/kernel/apic/apic.c:1091
asm_sysvec_apic_timer_interrupt+0x12/0x20 arch/x86/include/asm/idtentry.h:631
native_safe_halt arch/x86/include/asm/irqflags.h:60 [inline]
arch_safe_halt arch/x86/include/asm/irqflags.h:103 [inline]
acpi_safe_halt drivers/acpi/processor_idle.c:111 [inline]
acpi_idle_do_entry drivers/acpi/processor_idle.c:517 [inline]
acpi_idle_enter+0x25b/0x2e0 drivers/acpi/processor_idle.c:648
cpuidle_enter_state+0x2bd/0x750 drivers/cpuidle/cpuidle.c:237
cpuidle_enter+0x3c/0x60 drivers/cpuidle/cpuidle.c:351
call_cpuidle kernel/sched/idle.c:158 [inline]
cpuidle_idle_call kernel/sched/idle.c:239 [inline]
do_idle+0x193/0x230 kernel/sched/idle.c:299
cpu_startup_entry+0x15/0x20 kernel/sched/idle.c:395
rest_init+0xd7/0xe0 init/main.c:721
arch_call_rest_init+0xa/0xb
start_kernel+0x5a0/0x625 init/main.c:1061
secondary_startup_64_no_verify+0xb0/0xbb

read to 0xffffffff86fc1ad0 of 4 bytes by task 0 on cpu 1:
tick_nohz_stop_tick+0x73/0x410 kernel/time/tick-sched.c:788
__tick_nohz_idle_stop_tick kernel/time/tick-sched.c:981 [inline]
tick_nohz_idle_stop_tick+0x148/0x2e0 kernel/time/tick-sched.c:1002
cpuidle_idle_call kernel/sched/idle.c:235 [inline]
do_idle+0x176/0x230 kernel/sched/idle.c:299
cpu_startup_entry+0x15/0x20 kernel/sched/idle.c:395
secondary_startup_64_no_verify+0xb0/0xbb

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.10.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================


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

[syzbot]

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