[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20251002082301.a20b2d5ea4379c33cd9c5953@kernel.org>
Date: Thu, 2 Oct 2025 08:23:01 +0900
From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: chenyuan_fl@....com, mhiramat@...nel.org, bigeasy@...utronix.de,
chenyuan@...inos.cn, john.ogness@...utronix.de,
linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
mathieu.desnoyers@...icios.com, rostedt@...dmis.org
Subject: Re: [PATCH v4] tracing: Fix race condition in kprobe initialization
causing NULL pointer dereference
On Wed, 1 Oct 2025 14:32:00 +0200
Peter Zijlstra <peterz@...radead.org> wrote:
> On Wed, Oct 01, 2025 at 03:20:25AM +0100, chenyuan_fl@....com wrote:
>
> >
> > v1->v2: Fix race analysis (per Masami) - kprobe arms in class->reg().
> > v2->v3: Adopt RELEASE/ACQUIRE semantics per Peter/John's suggestions,
> > aligning with Steven's clarification on barrier purposes.
> > v3->v4: Introduce load_flag() (Masami) and optimize barrier usage in
> > checks/clear (Peter).
>
> Stuff like this ought to go below the --- such that git-am and similar
> tools throw it out.
Yeah, let me remove it manually this time.
Yuan, please put changelogs like below next time:
---
v1->v2: Fix race analysis (per Masami) - kprobe arms in class->reg().
...
Thank you,
--
Masami Hiramatsu (Google) <mhiramat@...nel.org>
Powered by blists - more mailing lists