[moderation] [perf?] KCSAN: data-race in __perf_event_read_value / perf_event_set_state (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9b2ffa6148b1 Merge tag 'mtd/fixes-for-6.13-rc5' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11c7e2f8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=87d3cfca6847d1fa
dashboard link: https://syzkaller.appspot.com/bug?extid=e5ee965be96aeb3bf530
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [ac...@kernel.org adrian...@intel.com alexander...@linux.intel.com iro...@google.com jo...@kernel.org kan....@linux.intel.com linux-...@vger.kernel.org linux-pe...@vger.kernel.org mark.r...@arm.com mi...@redhat.com namh...@kernel.org pet...@infradead.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8f3f5cceed80/disk-9b2ffa61.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1ba00b70d91e/vmlinux-9b2ffa61.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b99c1bb4d63f/bzImage-9b2ffa61.xz

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

==================================================================
BUG: KCSAN: data-race in __perf_event_read_value / perf_event_set_state

write to 0xffff88812d9c6380 of 8 bytes by task 10380 on cpu 0:
perf_event_update_time kernel/events/core.c:675 [inline]
perf_event_set_state+0x175/0x3f0 kernel/events/core.c:694
event_sched_out+0x2c8/0x4a0 kernel/events/core.c:2335
group_sched_out kernel/events/core.c:2359 [inline]
__pmu_ctx_sched_out+0x3aa/0x4e0 kernel/events/core.c:3339
ctx_sched_out+0x267/0x2c0 kernel/events/core.c:3420
task_ctx_sched_out kernel/events/core.c:2739 [inline]
perf_event_context_sched_out kernel/events/core.c:3664 [inline]
__perf_event_task_sched_out+0x438/0x1010 kernel/events/core.c:3763
perf_event_task_sched_out include/linux/perf_event.h:1540 [inline]
prepare_task_switch kernel/sched/core.c:5173 [inline]
context_switch kernel/sched/core.c:5316 [inline]
__schedule+0x8f6/0x930 kernel/sched/core.c:6756
__schedule_loop kernel/sched/core.c:6833 [inline]
schedule+0x55/0xc0 kernel/sched/core.c:6848
futex_wait_queue kernel/futex/waitwake.c:370 [inline]
__futex_wait+0x141/0x290 kernel/futex/waitwake.c:669
futex_wait+0x99/0x1c0 kernel/futex/waitwake.c:697
do_futex+0x276/0x370 kernel/futex/syscalls.c:102
__do_sys_futex kernel/futex/syscalls.c:179 [inline]
__se_sys_futex+0x25d/0x3a0 kernel/futex/syscalls.c:160
__x64_sys_futex+0x78/0x90 kernel/futex/syscalls.c:160
x64_sys_call+0x2d6a/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:203
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff88812d9c6380 of 8 bytes by task 10387 on cpu 1:
__perf_event_read_value+0x84/0x1c0 kernel/events/core.c:5599
perf_read_one kernel/events/core.c:5756 [inline]
__perf_read kernel/events/core.c:5809 [inline]
perf_read+0x174/0x4a0 kernel/events/core.c:5826
loop_rw_iter+0x237/0x360
io_iter_do_read io_uring/rw.c:772 [inline]
__io_read+0xa5a/0xaf0 io_uring/rw.c:869
io_read+0x1e/0x60 io_uring/rw.c:947
io_issue_sqe+0x150/0xc10 io_uring/io_uring.c:1740
io_wq_submit_work+0x3eb/0x540 io_uring/io_uring.c:1849
io_worker_handle_work+0x486/0x9d0 io_uring/io-wq.c:601
io_wq_worker+0x286/0x820 io_uring/io-wq.c:655
ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

value changed: 0x000000000786fbce -> 0x000000000787c873

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 10387 Comm: iou-wrk-10380 Not tainted 6.13.0-rc4-syzkaller-00012-g9b2ffa6148b1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/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.