Linux Perf Users
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Baisheng Gao <baisheng.gao@unisoc.com>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	"reviewer:PERFORMANCE EVENTS SUBSYSTEM"
	<kan.liang@linux.intel.com>,
	"open list:PERFORMANCE EVENTS SUBSYSTEM"
	<linux-perf-users@vger.kernel.org>,
	"open list:PERFORMANCE EVENTS SUBSYSTEM"
	<linux-kernel@vger.kernel.org>,
	cixi.geng@linux.dev, hao_hao.wang@unisoc.com
Subject: Re: [PATCH] perf/core: Handling the race between exit_mmap and perf sample
Date: Wed, 4 Jun 2025 15:55:01 +0100	[thread overview]
Message-ID: <aEBeRfScZKD-7h5u@J2N7QTR9R3> (raw)
In-Reply-To: <20250604142437.GM38114@noisy.programming.kicks-ass.net>

On Wed, Jun 04, 2025 at 04:24:37PM +0200, Peter Zijlstra wrote:
> On Wed, Jun 04, 2025 at 03:05:43PM +0100, Mark Rutland wrote:
> 
> > Loooking at 5.15.149 and current HEAD (5abc7438f1e9), do_exit() calls
> > exit_mm() before perf_event_exit_task(), so it looks
> > like perf could sample from another task's mm.
> > 
> > Yuck.
> > 
> > Peter, does the above sound plausible to you?
> 
> Yuck indeed. And yeah, we should probably re-arrange things there.
> 
> Something like so?

That should plumb the hole for task-bound events, yep.

I think we might need something in the perf core for cpu-bound events, assuming
those can also potentially make samples.

From a quick scan of perf_event_sample_format:

	PERF_SAMPLE_IP			// safe
	PERF_SAMPLE_TID			// safe
	PERF_SAMPLE_TIME		// safe
	PERF_SAMPLE_ADDR		// ???
	PERF_SAMPLE_READ		// ???
	PERF_SAMPLE_CALLCHAIN		// may access mm
	PERF_SAMPLE_ID			// safe
	PERF_SAMPLE_CPU			// safe
	PERF_SAMPLE_PERIOD		// safe
	PERF_SAMPLE_STREAM_ID		// ???
	PERF_SAMPLE_RAW			// ???
	PERF_SAMPLE_BRANCH_STACK	// safe
	PERF_SAMPLE_REGS_USER		// safe
	PERF_SAMPLE_STACK_USER		// may access mm
	PERF_SAMPLE_WEIGHT		// ???
	PERF_SAMPLE_DATA_SRC		// ???
	PERF_SAMPLE_IDENTIFIER		// safe
	PERF_SAMPLE_TRANSACTION		// ???
	PERF_SAMPLE_REGS_INTR		// safe
	PERF_SAMPLE_PHYS_ADDR		// safe; handles mm==NULL && addr < TASK_SIZE
	PERF_SAMPLE_AUX			// ???
	PERF_SAMPLE_CGROUP		// safe
	PERF_SAMPLE_DATA_PAGE_SIZE	// partial; doesn't check addr < TASK_SIZE
	PERF_SAMPLE_CODE_PAGE_SIZE	// partial; doesn't check addr < TASK_SIZE
	PERF_SAMPLE_WEIGHT_STRUCT	// ???

... I think all the dodgy cases use mm somehow, so maybe the perf core
should check for current->mm?

> 
> ---
> diff --git a/kernel/exit.c b/kernel/exit.c
> index 38645039dd8f..3407c16fc5a3 100644
> --- a/kernel/exit.c
> +++ b/kernel/exit.c
> @@ -944,6 +944,15 @@ void __noreturn do_exit(long code)
>  	taskstats_exit(tsk, group_dead);
>  	trace_sched_process_exit(tsk, group_dead);
>  
> +	/*
> +	 * Since samping can touch ->mm, make sure to stop everything before we

Typo: s/samping/sampling/

> +	 * tear it down.
> +	 *
> +	 * Also flushes inherited counters to the parent - before the parent
> +	 * gets woken up by child-exit notifications.
> +	 */
> +	perf_event_exit_task(tsk);
> +
>  	exit_mm();
>  
>  	if (group_dead)
> @@ -959,14 +968,6 @@ void __noreturn do_exit(long code)
>  	exit_task_work(tsk);
>  	exit_thread(tsk);
>  
> -	/*
> -	 * Flush inherited counters to the parent - before the parent
> -	 * gets woken up by child-exit notifications.
> -	 *
> -	 * because of cgroup mode, must be called before cgroup_exit()
> -	 */
> -	perf_event_exit_task(tsk);
> -
>  	sched_autogroup_exit_task(tsk);
>  	cgroup_exit(tsk);
>  

Otherwise, that looks good to me!

Mark.

  reply	other threads:[~2025-06-04 14:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24  2:54 [PATCH] perf/core: Handling the race between exit_mmap and perf sample Baisheng Gao
2025-04-24 10:40 ` Peter Zijlstra
2025-06-04 14:05 ` Mark Rutland
2025-06-04 14:24   ` Peter Zijlstra
2025-06-04 14:55     ` Mark Rutland [this message]
2025-06-04 15:32       ` Peter Zijlstra
2025-06-04 16:08         ` Mark Rutland
2025-06-05 11:08           ` Peter Zijlstra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aEBeRfScZKD-7h5u@J2N7QTR9R3 \
    --to=mark.rutland@arm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=baisheng.gao@unisoc.com \
    --cc=cixi.geng@linux.dev \
    --cc=hao_hao.wang@unisoc.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox