Linux Trace Kernel
 help / color / mirror / Atom feed
From: "Jérémy Jean" <jeremy.jean@oss.cyber.gouv.fr>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
	include@grrlz.net, linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing/user_events: Clear copied tracing state before fork duplication
Date: Wed, 26 Aug 2026 23:48:34 +0200	[thread overview]
Message-ID: <36329aac30d057120f95933c5ef7dec1@oss.cyber.gouv.fr> (raw)
In-Reply-To: <20260826152312.62d5802e@gandalf.local.home>

On 2026-08-26 21:23, Steven Rostedt wrote:
>> diff --git a/include/linux/user_events.h b/include/linux/user_events.h
>> index 57d1ff0..2c9ac7b 100644
>> --- a/include/linux/user_events.h
>> +++ b/include/linux/user_events.h
>> @@ -48,6 +48,7 @@ static inline void user_events_fork(struct 
>> task_struct *t,
>>  		return;
>>  	}
>> 
>> +	t->user_event_mm = NULL;
> 
> Honestly, that line should be in user_event_mm_dup() and not here.

Thanks for the feedback. I have just sent a v2 implementing this.

Regards,
Jérémy

  reply	other threads:[~2026-08-26 21:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 21:10 [PATCH] tracing/user_events: Clear copied tracing state before fork duplication Jérémy Jean
2026-08-24 23:49 ` Bradley Morgan
2026-08-26 19:23 ` Steven Rostedt
2026-08-26 21:48   ` Jérémy Jean [this message]
     [not found] <20260824210814.3726486-2-Jeremy.Jean@oss.cyber.gouv.fr>
     [not found] ` <20260824215040.0509ff1b@fedora>
2026-08-25 14:44   ` Steven Rostedt
2026-08-25 14:46     ` Bradley Morgan

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=36329aac30d057120f95933c5ef7dec1@oss.cyber.gouv.fr \
    --to=jeremy.jean@oss.cyber.gouv.fr \
    --cc=include@grrlz.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.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