From: Oleg Nesterov <oleg@redhat.com>
To: Wen Yang <wenyang.linux@foxmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] get_signal: simplify/cleanup the the usage of ksig->info
Date: Fri, 23 Feb 2024 15:19:29 +0100 [thread overview]
Message-ID: <20240223141928.GB8267@redhat.com> (raw)
In-Reply-To: <tencent_7C50F304C14CB2A5133317F8A13D1F544D0A@qq.com>
On 02/23, Wen Yang wrote:
>
>
> On 2024/2/23 18:50, Oleg Nesterov wrote:
> >get_signal() uses signr or ksig->info.si_signo in a chaotic way, this
> >looks confusing. Change it to always use signr.
> >
> >This allows us to simplify the SIGNAL_GROUP_EXIT/group_exec_task branch,
> >it no longer needs to touch ksig at all.
> >
> >Signed-off-by: Oleg Nesterov <oleg@redhat.com>
> >---
> > kernel/signal.c | 15 +++++++++------
> > 1 file changed, 9 insertions(+), 6 deletions(-)
> >
> >diff --git a/kernel/signal.c b/kernel/signal.c
> >index c9c57d053ce4..690982e6595e 100644
> >--- a/kernel/signal.c
> >+++ b/kernel/signal.c
> >@@ -2727,12 +2727,15 @@ bool get_signal(struct ksignal *ksig)
> > /* Has this task already been marked for death? */
> > if ((signal->flags & SIGNAL_GROUP_EXIT) ||
> > signal->group_exec_task) {
> >- clear_siginfo(&ksig->info);
> >- ksig->info.si_signo = signr = SIGKILL;
> >+ signr = SIGKILL;
> > sigdelset(¤t->pending.signal, SIGKILL);
> > trace_signal_deliver(SIGKILL, SEND_SIG_NOINFO,
> >- &sighand->action[SIGKILL - 1]);
> >+ &sighand->action[SIGKILL - 1]);
> > recalc_sigpending();
> >+ /*
> >+ * implies do_group_exit(), no need to initialize
> >+ * ksig->info
> >+ */
> > goto fatal;
>
> There is little question:
> If the this conditions is met:
> current->flags & PF_USER_WORKER
> It may execute “goto out“ instead of do_group_exit().
Yes, but vhost/io workers do not use ksig at all.
Oleg.
next prev parent reply other threads:[~2024-02-23 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 10:50 [PATCH] get_signal: simplify/cleanup the the usage of ksig->info Oleg Nesterov
2024-02-23 13:41 ` Wen Yang
2024-02-23 14:19 ` Oleg Nesterov [this message]
2024-02-23 14:31 ` Oleg Nesterov
2024-02-23 14:44 ` Oleg Nesterov
2024-02-26 9:52 ` Oleg Nesterov
2024-02-26 15:06 ` Wen Yang
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=20240223141928.GB8267@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wenyang.linux@foxmail.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 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.