From: Andrew Morton <akpm@linux-foundation.org>
To: Bradley Morgan <include@grrlz.net>
Cc: Oleg Nesterov <oleg@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] signal: change sys_kill() to use SEND_SIG_NOINFO
Date: Sun, 28 Jun 2026 12:17:41 -0700 [thread overview]
Message-ID: <20260628121741.12a375ceaf9ba6f6a3ac51eb@linux-foundation.org> (raw)
In-Reply-To: <F6C09C27-A8F3-4B73-8CF9-148D8ADC5D13@grrlz.net>
On Sun, 28 Jun 2026 19:01:53 +0100 Bradley Morgan <include@grrlz.net> wrote:
> >TODO: kill prepare_kill_siginfo() and change other users to use
> >SEND_SIG_NOINFO too. This needs trivial changes in __send_signal_locked()
> >and TP_STORE_SIGINFO().
> >
> >Link: https://lore.kernel.org/all/20260622164029.11474-1-include@grrlz.net/ [1]
> >Signed-off-by: Oleg Nesterov <oleg@redhat.com>
>
> Code wise, please add my tag.
>
> Reviewed-by: Bradley Morgan <include@grrlz.net>
Thanks.
I updated the changelog for this patch.
> I would do acked by personally but no idea if that's liked over in this
> subsystm
Both are liked ;)
fwiw, I consider Reviewed-by to be stronger than Acked-by. I suspect
the latter sometimes means "cool changelog!".
> Description wise, I'm sure that looks fine
>
>
> Andrew, could you please take my fix?
There are many fixes, so please be specific to help avoid mistakes!
I think you're referring to
https://lore.kernel.org/all/86a8857d58d43ee26a8b365b837fd24830343494.1782159692.git.include@grrlz.net/
prev parent reply other threads:[~2026-06-28 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 15:33 Oleg Nesterov
2026-06-26 16:36 ` Andrew Morton
2026-06-26 16:49 ` Bradley Morgan
2026-06-28 17:51 ` Oleg Nesterov
2026-06-28 18:01 ` Bradley Morgan
2026-06-28 18:19 ` Oleg Nesterov
2026-06-28 19:17 ` Andrew Morton [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=20260628121741.12a375ceaf9ba6f6a3ac51eb@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=include@grrlz.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
/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®