From: "Eric W. Biederman" <ebiederm@xmission.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Avi Weiss <thnkslprpt@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] signal: respect the blocked mask in dequeue_synchronous_signal()
Date: Thu, 22 Oct 2026 20:21:26 +0000 [thread overview]
Message-ID: <878q3po5a1.fsf@email.froward.int.ebiederm.org> (raw)
In-Reply-To: <atn6anj4NRKpT-qN@redhat.com> (Oleg Nesterov's message of "Thu, 22 Oct 2026 13:58:34 +0200")
Oleg Nesterov <oleg@redhat.com> writes:
> I was going to send another cleanup on top of this fix. Can't do this today,
> but let me explain... It is a bit ugly to check si_signo twice.
I can see where your proposed change is addressing that and it seems
reasonable.
> And afaics we have another problem. sys_rt_sigqueueinfo() allows to
> send a SI_FROMKERNEL RT signal to itself.
I don't see where your proposed code is addressing this.
From 10,000 feet I think it is deliberate that we allow sending all
possible pending signals to ourselves. Some version of that is
necessary to restore a checkpoint of a process, if it has not
yet handled the signal at the point it is check-pointed.
You can look at CRIU if you need to see if this is behavior that
is being relied upon.
> In this case sigmask(q->info.si_signo) leads to UB on 32-bit.
I presume you are referring to a signal number that exceeds 32
being put into a 32bit mask. That does seem worth fixing.
Eric
> I'll recheck, write the changelog, and send something like below tomorrow.
> perhaps rt_sigmask() makes more sense than sigset_t...
>
> Oleg.
>
>
> From 6f7441ff08d7b88b96ac6787b40634e8c173003c Mon Sep 17 00:00:00 2001
> From: Oleg Nesterov <oleg@redhat.com>
> Date: Thu, 22 Oct 2026 13:43:01 +0200
> Subject: [PATCH] signal: cleanup the .si_signo checks in dequeue_synchronous_signal()
>
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>
> ---
> kernel/signal.c | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/signal.c b/kernel/signal.c
> index 7386b9552dc3..9cfd4d03cad4 100644
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -676,21 +676,24 @@ static int dequeue_synchronous_signal(kernel_siginfo_t *info)
> struct task_struct *tsk = current;
> struct sigpending *pending = &tsk->pending;
> struct sigqueue *q, *sync = NULL;
> + unsigned long mask;
> + sigset_t xxx;
>
> /*
> * Might a synchronous signal be in the queue?
> */
> - if (!((pending->signal.sig[0] & ~tsk->blocked.sig[0]) & SYNCHRONOUS_MASK))
> + mask = (pending->signal.sig[0] & ~tsk->blocked.sig[0]) & SYNCHRONOUS_MASK;
> + if (!mask)
> return 0;
>
> + siginitset(&xxx, mask);
> /*
> * Return the first synchronous signal in the queue.
> */
> list_for_each_entry(q, &pending->list, list) {
> /* Synchronous signals have a positive si_code */
> - if ((q->info.si_code > SI_USER) &&
> - (sigmask(q->info.si_signo) & SYNCHRONOUS_MASK) &&
> - !sigismember(&tsk->blocked, q->info.si_signo)) {
> + if (SI_FROMKERNEL(&q->info) &&
> + sigismember(&xxx, q->info.si_signo)) {
> sync = q;
> goto next;
> }
next prev parent reply other threads:[~2026-10-22 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 6:10 Avi Weiss
2026-10-22 11:58 ` Oleg Nesterov
2026-10-22 20:21 ` Eric W. Biederman [this message]
2026-10-22 20:15 ` Eric W. Biederman
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=878q3po5a1.fsf@email.froward.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=thnkslprpt@gmail.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®