Linux Trace Kernel
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Jérémy Jean" <jeremy.jean@oss.cyber.gouv.fr>
Cc: Bradley Morgan <brads@mainlining.org>,
	mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] tracing/user_events: Clear copied tracing state before fork duplication
Date: Thu, 27 Aug 2026 08:42:05 -0400	[thread overview]
Message-ID: <20260827084205.776f7cb7@gandalf.local.home> (raw)
In-Reply-To: <3beb0339407a35c0b995856eae74d870@oss.cyber.gouv.fr>

On Thu, 27 Aug 2026 14:27:44 +0200
Jérémy Jean <jeremy.jean@oss.cyber.gouv.fr> wrote:

> Thanks for this. I thought that my previous version was okay
> so that it was not required to read the details of
> user_event_mm_alloc() to get convinced whether user_event_mm is
> accessed or not, but it's true that in the end, this is not
> required. Your fix is simpler. Do you want me to send a v3
> with that simplification and the same changelog as in the v2?

Yes, please send a v3.

Thanks,

-- Steve

      parent reply	other threads:[~2026-08-27 12:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 21:44 [PATCH v2] tracing/user_events: Clear copied tracing state before fork duplication Jérémy Jean
2026-08-26 22:37 ` Bradley Morgan
2026-08-27  7:15   ` Jérémy Jean
2026-08-27  9:45     ` Bradley Morgan
2026-08-27 12:15       ` Steven Rostedt
2026-08-27 12:17         ` Bradley Morgan
2026-08-27 12:08 ` Steven Rostedt
2026-08-27 12:09   ` Bradley Morgan
2026-08-27 12:19     ` Steven Rostedt
2026-08-27 12:24       ` Bradley Morgan
2026-08-27 12:27       ` Jérémy Jean
2026-08-27 12:29         ` Bradley Morgan
2026-08-27 12:43           ` Steven Rostedt
2026-08-27 12:44             ` Bradley Morgan
2026-08-27 12:42         ` Steven Rostedt [this message]

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=20260827084205.776f7cb7@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=brads@mainlining.org \
    --cc=jeremy.jean@oss.cyber.gouv.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=stable@vger.kernel.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