From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org,
Michael Bommarito <michael.bommarito@gmail.com>
Subject: Re: Please consider fb3bbcfe344e ("exit: change the release_task() paths to call flush_sigqueue() lockless") for 5.10.y, 5.15.y, 6.1.y, 6.6.y, and 6.12.y
Date: Fri, 10 Jul 2026 17:03:11 -0400 [thread overview]
Message-ID: <20260710163023.agent5-0015@kernel.org> (raw)
In-Reply-To: <20260710023120.3747693-1-michael.bommarito@gmail.com>
On Thu, Jul 09, 2026 at 10:31:20PM -0400, Michael Bommarito wrote:
> Upstream commit: fb3bbcfe344e64a46574a638b051ffd78762c12d
> Subject: exit: change the release_task() paths to call flush_sigqueue() lockless
>
> Backport note:
> The mechanical check above reports whether the upstream diff applies to
> each listed branch as-is. In this refresh, the upstream diff applies
> cleanly to the file snapshots for all requested series.
The diff applies cleanly, but it isn't safe on any of the requested
branches. The commit's correctness depends on the v6.13+ posix-timer
rework (6017a158beb1 "posix-timers: Embed sigqueue in struct k_itimer"
and friends), after which timer deletion no longer clears
SIGQUEUE_PREALLOC or frees tmr->sigq behind the exiting task's back.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-10 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 2:31 Please consider fb3bbcfe344e ("exit: change the release_task() paths to call flush_sigqueue() lockless") for 5.10.y, 5.15.y, 6.1.y, 6.6.y, and 6.12.y Michael Bommarito
2026-07-10 21:03 ` Sasha Levin [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=20260710163023.agent5-0015@kernel.org \
--to=sashal@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.bommarito@gmail.com \
--cc=stable@vger.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 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.