[moderation] [kernel?] KCSAN: data-race in hrtimer_reprogram / print_cpu (10)

0 views
Skip to first unread message

syzbot

unread,
Apr 26, 2024, 7:32:32 AM (10 days ago) Apr 26
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c942a0cd3603 Merge tag 'for_linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13df7a9b180000
kernel config: https://syzkaller.appspot.com/x/.config?x=4128b708dfac799b
dashboard link: https://syzkaller.appspot.com/bug?extid=27b6f0842a11090153fe
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [anna-...@linutronix.de fred...@kernel.org linux-...@vger.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/0ccaed2938dd/disk-c942a0cd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f45fb1a92144/vmlinux-c942a0cd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9ff8e1609ba0/bzImage-c942a0cd.xz

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

==================================================================
BUG: KCSAN: data-race in hrtimer_reprogram / print_cpu

write to 0xffff888237c1ffa0 of 8 bytes by task 9227 on cpu 0:
__hrtimer_reprogram kernel/time/hrtimer.c:662 [inline]
hrtimer_reprogram+0x1a2/0x220 kernel/time/hrtimer.c:869
hrtimer_start_range_ns+0x4ee/0x560 kernel/time/hrtimer.c:1306
hrtimer_start_expires include/linux/hrtimer.h:289 [inline]
hrtimer_sleeper_start_expires kernel/time/hrtimer.c:1972 [inline]
do_nanosleep+0x86/0x300 kernel/time/hrtimer.c:2048
hrtimer_nanosleep+0xe8/0x1e0 kernel/time/hrtimer.c:2104
common_nsleep+0x68/0x90 kernel/time/posix-timers.c:1350
__do_sys_clock_nanosleep kernel/time/posix-timers.c:1396 [inline]
__se_sys_clock_nanosleep+0x20a/0x240 kernel/time/posix-timers.c:1373
__x64_sys_clock_nanosleep+0x55/0x70 kernel/time/posix-timers.c:1373
x64_sys_call+0x2489/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:231
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888237c1ffa0 of 8 bytes by task 10551 on cpu 1:
print_cpu+0x2fb/0x670 kernel/time/timer_list.c:133
timer_list_show+0x115/0x180 kernel/time/timer_list.c:295
seq_read_iter+0x65b/0x940 fs/seq_file.c:272
proc_reg_read_iter+0x11e/0x190 fs/proc/inode.c:299
call_read_iter include/linux/fs.h:2104 [inline]
copy_splice_read+0x3a4/0x5d0 fs/splice.c:365
do_splice_read fs/splice.c:985 [inline]
splice_direct_to_actor+0x26c/0x670 fs/splice.c:1089
do_splice_direct_actor fs/splice.c:1207 [inline]
do_splice_direct+0xd7/0x150 fs/splice.c:1233
do_sendfile+0x3b9/0x970 fs/read_write.c:1295
__do_sys_sendfile64 fs/read_write.c:1362 [inline]
__se_sys_sendfile64 fs/read_write.c:1348 [inline]
__x64_sys_sendfile64+0x110/0x150 fs/read_write.c:1348
x64_sys_call+0x2c67/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:41
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x00000033d3fe7200 -> 0x00000033d3e1ea7a

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 10551 Comm: syz-executor.0 Tainted: G W 6.9.0-rc5-syzkaller-00159-gc942a0cd3603 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/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
Reply all
Reply to author
Forward
0 new messages