From: "Eric W. Biederman" <ebiederm@xmission.com>
To: Thomas Gleixner <tglx@kernel.org>
Cc: Oleg Nesterov <oleg@redhat.com>,
Frederic Weisbecker <frederic@kernel.org>,
Hyunwoo Kim <imv4bel@gmail.com>,
brauner@kernel.org, peterz@infradead.org,
anna-maria@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] signal: Use list_del_init_careful() in flush_sigqueue()
Date: Sun, 30 Aug 2026 17:04:09 -0500 [thread overview]
Message-ID: <87zey3fep2.fsf@email.froward.int.ebiederm.org> (raw)
In-Reply-To: <871pbfeaiv.ffs@fw13> (Thomas Gleixner's message of "Sun, 30 Aug 2026 20:19:36 +0200")
Thomas Gleixner <tglx@kernel.org> writes:
> On Fri, Aug 28 2026 at 00:56, Thomas Gleixner wrote:
>> On Thu, Aug 27 2026 at 13:43, Eric W. Biederman wrote:
>>> The obvious place to clean up task::pending i.e. signals is in
>>> exit_signals().
>>>
>>> I expect if I read through the history again that I would find that
>>> exit_signals() used to call flush_sigqueue, and that during the addition
>>> of posix thread signal handling flush_sigqueue was moved into
>>> __exit_signal in release_task because knowing if the entire thread group
>>> is dead was not available during that part of 2.5.
>>>
>>> We should honor PF_EXITING on a task and simply stop delivering
>>> signals to it. Today the code goes halfway there and does not
>>> set sig-pending after PF_EXITING is set.
>>
>> If flushing tsk::pending in exit_signals() is safe and stopping signals
>> to be queued when PF_EXITING is observed under sighand lock, then sure
>> that's the right thing to do. I'll look into that tomorrow.
>
> By some definition of tomorrow. :)
>
> Something like the below?
Yes.
It all comes after
ptrace_event(PTRACE_EVENT_EXIT, code) and
coredump_task_exit(tsk, core_state)
so should be completely invisible to userspace.
I don't see any problems with your proposed patch.
I am pondering what it would take to move
"flush_sigqueue(&p->signal->shared_pending);"
into do_exit in the group_dead case.
Perhaps exit_signals could perform the decrement of signal->live
and return group_dead. If so all of the work could be performed
in exit_signals(). As a follow-on change of cource.
But before I even propose something like that I have another change
in this area that I need to post.
Eric
> ---
> --- a/kernel/exit.c
> +++ b/kernel/exit.c
> @@ -299,12 +299,13 @@ void release_task(struct task_struct *p)
> free_pids(post.pids);
> release_thread(p);
> /*
> - * This task was already removed from the process/thread/pid lists
> - * and lock_task_sighand(p) can't succeed. Nobody else can touch
> - * ->pending or, if group dead, signal->shared_pending. We can call
> - * flush_sigqueue() lockless.
> + * This task was already removed from the process/thread/pid lists and
> + * lock_task_sighand(p) can't succeed. If it's the group leader then
> + * flush tsk->signal->shared_pending. tsk->pending has been flushed
> + * already in exit_signals(). Nothing else can touch
> + * signal->shared_pending anymore, so flush_sigqueue() can be invoked
> + * lockless.
> */
> - flush_sigqueue(&p->pending);
> if (thread_group_leader(p))
> flush_sigqueue(&p->signal->shared_pending);
>
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -1030,6 +1030,10 @@ static int __send_signal_locked(int sig,
> lockdep_assert_held(&t->sighand->siglock);
>
> result = TRACE_SIGNAL_IGNORED;
> +
> + if (unlikely(type == PIDTYPE_PID && (t->flags & PF_EXITING)))
> + goto ret;
> +
> if (!prepare_signal(sig, t, force))
> goto ret;
>
> @@ -1990,6 +1994,9 @@ void posixtimer_send_sigqueue(struct k_i
> if (!likely(lock_task_sighand(t, &flags)))
> return;
>
> + if (unlikely(tmr->it_pid_type == PIDTYPE_PID && (t->flags & PF_EXITING)))
> + return;
> +
> /*
> * Update @tmr::sigqueue_seq for posix timer signals with sighand
> * locked to prevent a race against dequeue_signal().
> @@ -3118,6 +3125,16 @@ static void retarget_shared_pending(stru
> }
> }
>
> +/*
> + * tsk::flags has PF_EXITING set which prevents signals to be queued for on
> + * tsk::pending. Nothing else can touch the tsk::pending anymore so it can be
> + * flushed lockless.
> + */
> +static inline void flush_pending_unlocked(struct task_struct *tsk)
> +{
> + flush_sigqueue(&tsk->pending);
> +}
> +
> void exit_signals(struct task_struct *tsk)
> {
> int group_stop = 0;
> @@ -3130,8 +3147,10 @@ void exit_signals(struct task_struct *ts
> cgroup_threadgroup_change_begin(tsk);
>
> if (thread_group_empty(tsk) || (tsk->signal->flags & SIGNAL_GROUP_EXIT)) {
> - tsk->flags |= PF_EXITING;
> + scoped_guard(spinlock_irq, &tsk->sighand->siglock)
> + tsk->flags |= PF_EXITING;
> cgroup_threadgroup_change_end(tsk);
> + flush_pending_unlocked(tsk);
> return;
> }
>
> @@ -3157,6 +3176,8 @@ void exit_signals(struct task_struct *ts
> out:
> spin_unlock_irq(&tsk->sighand->siglock);
>
> + flush_pending_unlocked(tsk);
> +
> /*
> * If group stop has completed, deliver the notification. This
> * should always go to the real parent of the group leader.
next prev parent reply other threads:[~2026-08-30 22:04 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 5:37 Hyunwoo Kim
2026-08-22 10:27 ` Bradley Morgan
2026-08-23 12:47 ` Oleg Nesterov
2026-08-24 2:53 ` Hyunwoo Kim
2026-08-24 8:28 ` Oleg Nesterov
2026-08-24 8:04 ` Thomas Gleixner
2026-08-24 9:45 ` Thomas Gleixner
2026-08-24 11:02 ` Oleg Nesterov
2026-08-24 11:54 ` Oleg Nesterov
2026-08-24 13:59 ` Frederic Weisbecker
2026-08-24 14:29 ` Oleg Nesterov
2026-08-25 16:58 ` Thomas Gleixner
2026-08-25 18:53 ` Oleg Nesterov
2026-08-25 19:58 ` Thomas Gleixner
2026-08-26 9:36 ` Oleg Nesterov
2026-08-26 19:19 ` Thomas Gleixner
2026-08-26 19:32 ` Oleg Nesterov
2026-08-27 3:29 ` Eric W. Biederman
2026-08-27 9:35 ` Thomas Gleixner
2026-08-27 18:43 ` Eric W. Biederman
2026-08-27 22:56 ` Thomas Gleixner
2026-08-30 18:19 ` Thomas Gleixner
2026-08-30 22:04 ` Eric W. Biederman [this message]
2026-08-31 9:53 ` Thomas Gleixner
2026-08-31 10:50 ` [PATCH] signal: Prevent exec() race Thomas Gleixner
2026-08-31 11:35 ` David Laight
2026-08-31 12:44 ` Oleg Nesterov
2026-09-01 12:49 ` Thomas Gleixner
2026-08-31 12:52 ` Frederic Weisbecker
2026-09-01 12:55 ` Thomas Gleixner
2026-09-01 13:27 ` Frederic Weisbecker
2026-09-01 15:14 ` Thomas Gleixner
2026-08-31 15:26 ` Eric W. Biederman
2026-09-01 13:35 ` Thomas Gleixner
2026-09-01 17:21 ` Eric W. Biederman
2026-09-01 18:40 ` [PATCH V2] " Thomas Gleixner
2026-09-02 10:28 ` Oleg Nesterov
2026-09-02 10:45 ` Oleg Nesterov
2026-09-03 6:09 ` Thomas Gleixner
2026-09-02 11:23 ` Oleg Nesterov
2026-09-02 14:19 ` Oleg Nesterov
2026-09-02 15:39 ` Eric W. Biederman
2026-09-02 17:08 ` Oleg Nesterov
2026-09-03 6:42 ` Thomas Gleixner
2026-09-03 7:29 ` Oleg Nesterov
2026-08-27 12:24 ` [PATCH] signal: Use list_del_init_careful() in flush_sigqueue() Thomas Gleixner
2026-08-27 17:51 ` Thomas Gleixner
2026-08-24 12:11 ` Thomas Gleixner
2026-08-24 16:31 ` Frederic Weisbecker
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=87zey3fep2.fsf@email.froward.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=anna-maria@linutronix.de \
--cc=brauner@kernel.org \
--cc=frederic@kernel.org \
--cc=imv4bel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
/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®