mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: jiang.kun2@zte.com.cn, "Eric W. Biederman" <ebiederm@xmission.com>
Cc: tglx@linutronix.de, frederic@kernel.org, peterz@infradead.org,
	brauner@kernel.org, joel.granados@kernel.org,
	viro@zeniv.linux.org.uk, lorenzo.stoakes@oracle.com,
	linux-kernel@vger.kernel.org, fan.yu9@zte.com.cn
Subject: Re: [PATCH] signal: Update send_signal_locked in relevant comments
Date: Fri, 11 Apr 2025 13:17:53 +0200	[thread overview]
Message-ID: <20250411111752.GB5322@redhat.com> (raw)
In-Reply-To: <20250411182448645tJ7XVmvNHqUXluy9xYQ_7@zte.com.cn>

On 04/11, jiang.kun2@zte.com.cn wrote:
>
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -2252,7 +2252,7 @@ bool do_notify_parent(struct task_struct *tsk, int sig)
>  			sig = 0;
>  	}
>  	/*
> -	 * Send with __send_signal as si_pid and si_uid are in the
> +	 * Send with __send_signal_locked as si_pid and si_uid are in the
>  	 * parent's namespaces.

Thanks, but I think that today this comment looks confusing either way.
It was added by 61e713bdca3678 along with this

	-               __group_send_sig_info(sig, &info, tsk->parent);
	+               __send_signal(sig, &info, tsk->parent, PIDTYPE_TGID, false);

change.

To me this comment looks outdated, perhaps it would be better to simply
remove it?

Or it should be updated to explain that we use __send_signal_locked()
instead of send_signal_locked() because the latter can wrongly change
si_pid/si_uid...

Oleg.


      reply	other threads:[~2025-04-11 11:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 10:24 jiang.kun2
2025-04-11 11:17 ` Oleg Nesterov [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=20250411111752.GB5322@redhat.com \
    --to=oleg@redhat.com \
    --cc=brauner@kernel.org \
    --cc=ebiederm@xmission.com \
    --cc=fan.yu9@zte.com.cn \
    --cc=frederic@kernel.org \
    --cc=jiang.kun2@zte.com.cn \
    --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=viro@zeniv.linux.org.uk \
    /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®