From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,oleg@redhat.com,mjguzik@gmail.com,akpm@linux-foundation.org,akpm@linux-foundation.org
Subject: [folded-merged] signal-avoid-clearing-tif_sigpending-in-recalc_sigpending-if-unset-fix.patch removed from -mm tree
Date: Sun, 16 Mar 2025 22:27:16 -0700 [thread overview]
Message-ID: <20250317052717.0F171C4CEEC@smtp.kernel.org> (raw)
The quilt patch titled
Subject: signal-avoid-clearing-tif_sigpending-in-recalc_sigpending-if-unset-fix
has been removed from the -mm tree. Its filename was
signal-avoid-clearing-tif_sigpending-in-recalc_sigpending-if-unset-fix.patch
This patch was dropped because it was folded into signal-avoid-clearing-tif_sigpending-in-recalc_sigpending-if-unset.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: signal-avoid-clearing-tif_sigpending-in-recalc_sigpending-if-unset-fix
Date: Mon Mar 3 02:22:48 PM PST 2025
add unlikely() as well
Cc: Mateusz Guzik <mjguzik@gmail.com>
Cc: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/signal.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/kernel/signal.c~signal-avoid-clearing-tif_sigpending-in-recalc_sigpending-if-unset-fix
+++ a/kernel/signal.c
@@ -177,7 +177,7 @@ static bool recalc_sigpending_tsk(struct
void recalc_sigpending(void)
{
if (!recalc_sigpending_tsk(current) && !freezing(current)) {
- if (test_thread_flag(TIF_SIGPENDING))
+ if (unlikely(test_thread_flag(TIF_SIGPENDING)))
clear_thread_flag(TIF_SIGPENDING);
}
}
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm-pgtable-convert-some-architectures-to-use-tlb_remove_ptdesc-v2-fix.patch
signal-avoid-clearing-tif_sigpending-in-recalc_sigpending-if-unset.patch
hung_task-show-the-blocker-task-if-the-task-is-hung-on-mutex-fix.patch
reply other threads:[~2025-03-17 5:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250317052717.0F171C4CEEC@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=mjguzik@gmail.com \
--cc=mm-commits@vger.kernel.org \
--cc=oleg@redhat.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.