From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: chenyuan_fl@163.com, mhiramat@kernel.org, bigeasy@linutronix.de,
chenyuan@kylinos.cn, john.ogness@linutronix.de,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, rostedt@goodmis.org
Subject: Re: [PATCH v4] tracing: Fix race condition in kprobe initialization causing NULL pointer dereference
Date: Thu, 2 Oct 2025 08:23:01 +0900 [thread overview]
Message-ID: <20251002082301.a20b2d5ea4379c33cd9c5953@kernel.org> (raw)
In-Reply-To: <20251001123200.GN4067720@noisy.programming.kicks-ass.net>
On Wed, 1 Oct 2025 14:32:00 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, Oct 01, 2025 at 03:20:25AM +0100, chenyuan_fl@163.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@kernel.org>
next prev parent reply other threads:[~2025-10-01 23:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 3:11 [PATCH] tracing: Fix race condition in kprobe initialization causing NULL pointer dereference chenyuan_fl
2025-09-29 5:39 ` Masami Hiramatsu
2025-09-29 6:57 ` [PATCH v2] " chenyuan_fl
2025-09-29 8:48 ` Steven Rostedt
2025-09-29 9:12 ` Peter Zijlstra
2025-09-29 9:32 ` John Ogness
2025-09-29 10:12 ` Peter Zijlstra
2025-09-30 8:58 ` Masami Hiramatsu
2025-09-30 10:10 ` Peter Zijlstra
2025-09-30 15:37 ` Masami Hiramatsu
2025-09-30 8:18 ` [PATH v3] " chenyuan_fl
2025-09-30 8:46 ` Peter Zijlstra
2025-09-30 15:37 ` Masami Hiramatsu
2025-10-01 2:20 ` [PATCH v4] " chenyuan_fl
2025-10-01 12:32 ` Peter Zijlstra
2025-10-01 14:31 ` Steven Rostedt
2025-10-01 22:59 ` Masami Hiramatsu
2025-10-02 14:04 ` Masami Hiramatsu
2025-10-01 23:23 ` Masami Hiramatsu [this message]
2025-09-30 9:13 ` [PATH v3] " John Ogness
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=20251002082301.a20b2d5ea4379c33cd9c5953@kernel.org \
--to=mhiramat@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=chenyuan@kylinos.cn \
--cc=chenyuan_fl@163.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).