From: Hao Wu <guoyuanchao1202@gmail.com>
To: brauner@kernel.org, ebiederm@xmission.com, keescook@chromium.org,
axboe@kernel.dk, peterz@infradead.org, elver@google.com,
tglx@linutronix.de, legion@kernel.org
Cc: linux-kernel@vger.kernel.org, Hao Wu <guoyuanchao1202@gmail.com>
Subject: [PATCH v1] signal.c: repeatedly set the TIF_SIGPENDING flag
Date: Wed, 23 Feb 2022 21:35:40 +0800 [thread overview]
Message-ID: <20220223133540.24230-1-guoyuanchao1202@gmail.com> (raw)
The recalc_sigpending_and_wake() function calls recalc_sigpending_tsk() and signal_wake_up(),
both of which set the TIF_SIGPENDING flag, so when recalc_sigpending_tsk() returns true,
the TIF_SIGPENDING flag will be set twice.
Maybe we can take away the set TIF_SIGPENDING logic from recalc_sigpending_tsk(),
so that recalc_sigpending_tsk() just determines whether the TIF_SIGPENDING flag needs to be set,
and the actual set TIF_SIGPENDING flag logic is executed outside.
kernel/signal.c:175: recalc_sigpending_and_wake()
kernel/signal.c:154: recalc_sigpending_tsk()
Signed-off-by: Hao Wu <guoyuanchao1202@gmail.com>
---
kernel/signal.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
index 9b04631acde8..6c5a00cd7e9a 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -157,7 +157,6 @@ static bool recalc_sigpending_tsk(struct task_struct *t)
PENDING(&t->pending, &t->blocked) ||
PENDING(&t->signal->shared_pending, &t->blocked) ||
cgroup_task_frozen(t)) {
- set_tsk_thread_flag(t, TIF_SIGPENDING);
return true;
}
@@ -181,8 +180,11 @@ void recalc_sigpending_and_wake(struct task_struct *t)
void recalc_sigpending(void)
{
- if (!recalc_sigpending_tsk(current) && !freezing(current))
+ if (recalc_sigpending_tsk(current)) {
+ set_tsk_thread_flag(t, TIF_SIGPENDING);
+ } else if (!freezing(current)) {
clear_thread_flag(TIF_SIGPENDING);
+ }
}
EXPORT_SYMBOL(recalc_sigpending);
@@ -2325,7 +2327,9 @@ static void ptrace_stop(int exit_code, int why, int clear_code, kernel_siginfo_t
* So check for any that we should take before resuming user mode.
* This sets TIF_SIGPENDING, but never clears it.
*/
- recalc_sigpending_tsk(current);
+ if (recalc_sigpending_tsk(current)) {
+ set_tsk_thread_flag(t, TIF_SIGPENDING);
+ }
}
static void ptrace_do_notify(int signr, int exit_code, int why)
2.32.0
next reply other threads:[~2022-02-23 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 13:35 Hao Wu [this message]
2022-06-06 14:33 ` Eric W. Biederman
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=20220223133540.24230-1-guoyuanchao1202@gmail.com \
--to=guoyuanchao1202@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=elver@google.com \
--cc=keescook@chromium.org \
--cc=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®