From: Oleg Nesterov <oleg@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: fan.yu9@zte.com.cn, frederic@kernel.org, peterz@infradead.org,
brauner@kernel.org, iro@zeniv.linux.org.uk,
joel.granados@kernel.org, lorenzo.stoakes@oracle.com,
linux-kernel@vger.kernel.org, xu.xin16@zte.com.cn,
yang.yang29@zte.com.cn
Subject: Re: [PATCH linux-next] signal: Remove outdated __send_signal references in do_notify_parent
Date: Mon, 28 Jul 2025 17:58:16 +0200 [thread overview]
Message-ID: <20250728155815.GB25567@redhat.com> (raw)
In-Reply-To: <878qk8pdkd.ffs@tglx>
On 07/28, Thomas Gleixner wrote:
>
> > --- a/kernel/signal.c
> > +++ b/kernel/signal.c
> > @@ -2251,10 +2251,7 @@ bool do_notify_parent(struct task_struct *tsk, int sig)
> > if (psig->action[SIGCHLD-1].sa.sa_handler == SIG_IGN)
> > sig = 0;
> > }
> > - /*
> > - * Send with __send_signal as si_pid and si_uid are in the
> > - * parent's namespaces.
> > - */
> > +
>
> Why are you removing the complete comment instead of just renaming the
> stale reference?
Then the comment should be updated to explain that we have to use
__send_signal_locked(), not send_signal_locked(), because the latter
can wrongly change si_pid/si_uid which are in the parent's namespace.
> commit 61e713bdca36 ("signal: Avoid corrupting si_pid and si_uid in
> do_notify_parent") put that comment there for a reason.
Yes, but the comment was a bit confusing, imo. I don't think it makes
the code more clear.
But I am fine either way.
Oleg.
next prev parent reply other threads:[~2025-07-28 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 8:24 fan.yu9
2025-07-28 9:54 ` [PATCH linux-next] signal: Remove outdated __send_signal references in? do_notify_parent Oleg Nesterov
2025-07-28 14:58 ` [PATCH linux-next] signal: Remove outdated __send_signal references in do_notify_parent Thomas Gleixner
2025-07-28 15:58 ` Oleg Nesterov [this message]
2025-07-29 7:04 ` fan.yu9
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=20250728155815.GB25567@redhat.com \
--to=oleg@redhat.com \
--cc=brauner@kernel.org \
--cc=fan.yu9@zte.com.cn \
--cc=frederic@kernel.org \
--cc=iro@zeniv.linux.org.uk \
--cc=joel.granados@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
/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®