From: Steven Rostedt <rostedt@goodmis.org>
To: Jeff Barnes <jeffbarnes@linux.microsoft.com>
Cc: Beau Belgrave <beaub@linux.microsoft.com>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>,
"mhiramat@kernel.org" <mhiramat@kernel.org>,
"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"kees@kernel.org" <kees@kernel.org>
Subject: Re: [PATCH] tracing/user_events: Fail fork when event state duplication fails
Date: Tue, 6 Oct 2026 10:14:27 -0400 [thread overview]
Message-ID: <20261006101427.25e0f8f7@fedora> (raw)
In-Reply-To: <0499A842-AA79-49A7-AAB5-47003DD799BE@getmailspring.com>
On Tue, 6 Oct 2026 09:42:39 -0400
Jeff Barnes <jeffbarnes@linux.microsoft.com> wrote:
> So in this case the state being duplicated during fork() is state that
> the application itself established. That's why I think propagating the
> allocation failure back through fork() is preferable to silently
> allowing the child to lose that state.
I agree.
-- Steve
prev parent reply other threads:[~2026-10-06 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 22:26 Jeff Barnes
2026-10-04 8:00 ` Steven Rostedt
2026-10-05 21:56 ` Beau Belgrave
2026-10-06 12:01 ` Jeff Barnes
2026-10-06 12:38 ` Steven Rostedt
2026-10-06 13:42 ` Jeff Barnes
2026-10-06 14:14 ` 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=20261006101427.25e0f8f7@fedora \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=beaub@linux.microsoft.com \
--cc=jeffbarnes@linux.microsoft.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@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
all inboxes | Powered by JetHome®