From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Bradley Morgan <include@grrlz.net>,
Christian Brauner <brauner@kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH -mm 0/1] signal: avoid unconditional siginfo copy in send_signal_locked()
Date: Sat, 4 Jul 2026 16:34:10 +0200 [thread overview]
Message-ID: <akkZ4mXxiX3ib0oq@redhat.com> (raw)
On top of
signal-avoid-shared-siginfo-namespace-rewrites.patch
in -mm tree.
To clarify, this (simple) change looks like a cleanup to me even if it slightly
complicates send_signal_locked(). But cleanups are always subjective, so I won't
argue if anyone thinks otherwise.
To remind, I think we should shift this namespace translation into
__send_signal_locked() -> copy_siginfo() path, but this needs something like
[PATCH v2 2/3] signal: turn the "bool force" arg of __send_signal_locked() into "int flags"
https://lore.kernel.org/all/ajVDzniRXROuyRgD@redhat.com/
Oleg.
next reply other threads:[~2026-07-04 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 14:34 Oleg Nesterov [this message]
2026-07-04 14:34 ` [PATCH -mm 1/1] signal: avoid unconditional siginfo copy in send_signal_locked() Oleg Nesterov
2026-07-04 14:46 ` Bradley Morgan
2026-07-06 9:11 ` Christian Brauner
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=akkZ4mXxiX3ib0oq@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=include@grrlz.net \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.