From: Josh Law <objecting@objecting.org>
To: Oleg Nesterov <oleg@redhat.com>,
Christian Brauner <brauner@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Gleixner <tglx@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, Josh Law <objecting@objecting.org>
Subject: [PATCH] signal: use task parameter instead of current in task_join_group_stop()
Date: Sun, 15 Mar 2026 15:18:47 +0000 [thread overview]
Message-ID: <20260315151847.214634-1-objecting@objecting.org> (raw)
task_join_group_stop() takes a task_struct parameter but reads jobctl
and signal from current instead. This works today because the sole
caller (copy_process) always passes a new thread in the same thread
group as current, so task->signal == current->signal and
task->jobctl is a copy of current->jobctl from dup_task_struct().
Use the task parameter directly so the function is self-consistent
with its API and will not silently break if a future caller passes a
task from a different thread group.
Signed-off-by: Josh Law <objecting@objecting.org>
---
kernel/signal.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
index 116cf678c4a3..cb417e3674ed 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -386,8 +386,8 @@ static bool task_participate_group_stop(struct task_struct *task)
void task_join_group_stop(struct task_struct *task)
{
- unsigned long mask = current->jobctl & JOBCTL_STOP_SIGMASK;
- struct signal_struct *sig = current->signal;
+ unsigned long mask = task->jobctl & JOBCTL_STOP_SIGMASK;
+ struct signal_struct *sig = task->signal;
if (sig->group_stop_count) {
sig->group_stop_count++;
--
2.34.1
next reply other threads:[~2026-03-15 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 15:18 Josh Law [this message]
2026-03-15 19:29 ` [PATCH] signal: use task parameter instead of current in task_join_group_stop() Oleg Nesterov
2026-03-15 19:50 ` Josh Law
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=20260315151847.214634-1-objecting@objecting.org \
--to=objecting@objecting.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--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 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.