From: Frederic Weisbecker <frederic@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: syzbot <syzbot+3c2e3cc60665d71de2f7@syzkaller.appspotmail.com>,
anna-maria@linutronix.de, linux-kernel@vger.kernel.org,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
Eric Biederman <ebiederm@xmission.com>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH] signal/posixtimers: Handle ignore/blocked sequences correctly
Date: Fri, 20 Dec 2024 14:06:31 +0100 [thread overview]
Message-ID: <Z2Vr1_85NucYkBaP@pavilion.home> (raw)
In-Reply-To: <87ikrf78xa.ffs@tglx>
Le Thu, Dec 19, 2024 at 08:46:25PM +0100, Thomas Gleixner a écrit :
> kernel/signal.c | 38 +++++++++++++++++++++++++++++---------
> 1 file changed, 29 insertions(+), 9 deletions(-)
>
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -2007,11 +2007,23 @@ void posixtimer_send_sigqueue(struct k_i
>
> if (!list_empty(&q->list)) {
> /*
> - * If task group is exiting with the signal already pending,
> - * wait for __exit_signal() to do its job. Otherwise if
> - * ignored, it's not supposed to be queued. Try to survive.
> + * The signal was ignored and blocked. The timer
> + * expiry queued it because blocked signals are
> + * queued independent of the ignored state.
> + *
> + * The unblocking set SIGPENDING, but the signal
> + * was not yet dequeued from the pending list,
> + * which would have put it back on the ignore list.
I must be missing something. I don't see dequeue_signal() checking if a signal
is ignored upon delivery.
> + * So prepare_signal() sees unblocked and ignored,
> + * which ends up here. Leave it queued like a
> + * regular signal.
> + *
> + * The same happens when the task group is exiting
> + * and the signal is already queued.
> + * prepare_signal() treats SIGNAL_GROUP_EXIT as
> + * ignored independent of its queued state. This
> + * gets cleaned up in __exit_signal().
> */
> - WARN_ON_ONCE(!(t->signal->flags & SIGNAL_GROUP_EXIT));
> goto out;
> }
>
> @@ -2046,17 +2058,25 @@ void posixtimer_send_sigqueue(struct k_i
> goto out;
> }
>
> - /* This should never happen and leaks a reference count */
> - if (WARN_ON_ONCE(!hlist_unhashed(&tmr->ignored_list)))
> - hlist_del_init(&tmr->ignored_list);
> -
> if (unlikely(!list_empty(&q->list))) {
> /* This holds a reference count already */
> result = TRACE_SIGNAL_ALREADY_PENDING;
> goto out;
> }
>
> - posixtimer_sigqueue_getref(q);
> + /*
> + * If the signal is on the ignore list, it got blocked after it was
> + * ignored earlier. But nothing lifted the ignore. Move it back to
> + * the pending list to be consistent with the regular signal
> + * handling. If it gets unblocked, it will be ignored again unless
I'm not sure about that. If I follow the sigprocmask() path, set_task_blocked()
doesn't take care about that. And later on, dequeue_signal() doesn't seem to
check either...
Thanks.
> + * a handler has been installed before unblocking. If it's not on
> + * the ignore list acquire a reference count.
> + */
> + if (likely(hlist_unhashed(&tmr->ignored_list)))
> + posixtimer_sigqueue_getref(q);
> + else
> + hlist_del_init(&tmr->ignored_list);
> +
> posixtimer_queue_sigqueue(q, t, tmr->it_pid_type);
> result = TRACE_SIGNAL_DELIVERED;
> out:
next prev parent reply other threads:[~2024-12-20 13:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 17:14 [syzbot] [kernel?] WARNING in posixtimer_send_sigqueue (2) syzbot
2024-12-19 19:46 ` [PATCH] signal/posixtimers: Handle ignore/blocked sequences correctly Thomas Gleixner
2024-12-20 13:06 ` Frederic Weisbecker [this message]
2024-12-20 13:14 ` Thomas Gleixner
2024-12-20 13:23 ` Frederic Weisbecker
2024-12-20 14:59 ` Thomas Gleixner
2025-01-14 17:28 ` [PATCH V2] " Thomas Gleixner
2025-01-15 0:49 ` Frederic Weisbecker
2025-01-15 17:19 ` [tip: timers/urgent] " tip-bot2 for Thomas Gleixner
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=Z2Vr1_85NucYkBaP@pavilion.home \
--to=frederic@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=syzbot+3c2e3cc60665d71de2f7@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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