Root Cause Analysis
The KCSAN data-race occurs in kernel/events/core.c between lockless reads of struct perf_event::state (enum perf_event_state) in perf_poll() and marked writes to the same field in perf_event_set_state().
Involved Functions and Fields
Mechanism
perf_poll() is invoked on a perf event file descriptor without holding ctx->lock (here via io_uring -> io_file_supports_nowait() -> vfs_poll()).
- At
kernel/events/core.c:6322 (and again at line 6327, as well as in is_event_hup() at line 6260), perf_poll() performs plain, unmarked reads of event->state:
if (event->state <= PERF_EVENT_STATE_REVOKED)
return EPOLLERR;
poll_wait(file, &event->waitq, wait);
if (event->state <= PERF_EVENT_STATE_REVOKED)
return EPOLLERR;
By contrast, line 6333 in the same function already uses READ_ONCE(event->state).
- Concurrently—or in this report, when task 5259 was preempted inside KCSAN's watchpoint delay in
perf_poll()—the context-switch path (prepare_task_switch() -> perf_event_task_sched_out() -> event_sched_out()) updates event->state under ctx->lock via perf_event_set_state():
WRITE_ONCE(event->state, state); /* kernel/events/core.c:790 */
- Because
perf_poll() reads event->state without READ_ONCE() while perf_event_set_state() writes to it concurrently under ctx->lock, KCSAN reports a data race between the marked write in perf_event_set_state() and the unmarked read in perf_poll().
Fix Direction
Use READ_ONCE(event->state) consistently for the lockless reads of event->state in perf_poll() (kernel/events/core.c:6322, 6327) and is_event_hup() (kernel/events/core.c:6260), matching line 6333 (and perf_event_read() / perf_sigtrap()).