From: NIIBE Yutaka <gniibe@fsij.org>
To: linux-kernel@vger.kernel.org
Cc: NIIBE Yutaka <gniibe@fsij.org>
Subject: [PATCH v2 4/4] signal/x86: Move nosig handling at the end of exit_to_usermode_loop.
Date: Thu, 22 Mar 2018 10:44:13 +0900 [thread overview]
Message-ID: <20180322014413.24099-5-gniibe@fsij.org> (raw)
In-Reply-To: <20180322014413.24099-1-gniibe@fsij.org>
Handling of restarting a system call for nosig should be done after
all possible calls of do_signal, to see if one of them actually
delivers signal or not.
Before this change, restarting a system call for nosig may be followed
by a call of handle_signal which would try to change the system call
returning -EINTR instead, but it is too late to do so.
In this patch, the function name of do_signal is changed, to avoid
breakage of building User Mode Linux.
Signed-off-by: NIIBE Yutaka <gniibe@fsij.org>
---
arch/x86/entry/common.c | 6 +++++-
arch/x86/include/asm/signal.h | 4 +++-
arch/x86/kernel/signal.c | 6 +++---
3 files changed, 11 insertions(+), 5 deletions(-)
diff --git a/arch/x86/entry/common.c b/arch/x86/entry/common.c
index 74f6eee15179..14e4da298887 100644
--- a/arch/x86/entry/common.c
+++ b/arch/x86/entry/common.c
@@ -137,6 +137,8 @@ static long syscall_trace_enter(struct pt_regs *regs)
static void exit_to_usermode_loop(struct pt_regs *regs, u32 cached_flags)
{
+ int sig_result = 0;
+
/*
* In order to return to user mode, we need to have IRQs off with
* none of EXIT_TO_USERMODE_LOOP_FLAGS set. Several of these flags
@@ -159,7 +161,7 @@ static void exit_to_usermode_loop(struct pt_regs *regs, u32 cached_flags)
/* deal with pending signal delivery */
if (cached_flags & _TIF_SIGPENDING)
- do_signal(regs);
+ sig_result |= do_signal_x86(regs);
if (cached_flags & _TIF_NOTIFY_RESUME) {
clear_thread_flag(TIF_NOTIFY_RESUME);
@@ -177,6 +179,8 @@ static void exit_to_usermode_loop(struct pt_regs *regs, u32 cached_flags)
if (!(cached_flags & EXIT_TO_USERMODE_LOOP_FLAGS))
break;
}
+ if (unlikely(sig_result == DO_SIGNAL_NOSIG))
+ nosig_restart_syscall(regs);
}
/* Called with IRQs disabled. */
diff --git a/arch/x86/include/asm/signal.h b/arch/x86/include/asm/signal.h
index 6517df6d9938..32a861950a63 100644
--- a/arch/x86/include/asm/signal.h
+++ b/arch/x86/include/asm/signal.h
@@ -34,8 +34,10 @@ typedef sigset_t compat_sigset_t;
#endif /* __ASSEMBLY__ */
#include <uapi/asm/signal.h>
+#define DO_SIGNAL_DELIVERED 1
+#define DO_SIGNAL_NOSIG 2
#ifndef __ASSEMBLY__
-extern void do_signal(struct pt_regs *regs);
+extern int do_signal_x86(struct pt_regs *regs);
extern void nosig_restart_syscall(struct pt_regs *regs);
#define __ARCH_HAS_SA_RESTORER
diff --git a/arch/x86/kernel/signal.c b/arch/x86/kernel/signal.c
index 9c24df5ca2d4..4a852aa60118 100644
--- a/arch/x86/kernel/signal.c
+++ b/arch/x86/kernel/signal.c
@@ -803,17 +803,17 @@ static inline unsigned long get_nr_restart_syscall(const struct pt_regs *regs)
* want to handle. Thus you cannot kill init even with a SIGKILL even by
* mistake.
*/
-void do_signal(struct pt_regs *regs)
+int do_signal_x86(struct pt_regs *regs)
{
struct ksignal ksig;
if (get_signal(&ksig)) {
/* Whee! Actually deliver the signal. */
handle_signal(&ksig, regs);
- return;
+ return DO_SIGNAL_DELIVERED;
}
- nosig_restart_syscall(regs);
+ return DO_SIGNAL_NOSIG;
}
void nosig_restart_syscall(struct pt_regs *regs)
--
2.11.0
prev parent reply other threads:[~2018-03-22 1:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 1:44 [PATCH v2 0/4] Fix no signal delivery at do_signal NIIBE Yutaka
2018-03-22 1:44 ` [PATCH v2 1/4] signal/x86: Factor out nosig handling NIIBE Yutaka
2018-03-22 1:44 ` [PATCH v2 2/4] signal/x86: do_signal: syscall restart should be done only once NIIBE Yutaka
2018-03-22 1:44 ` [PATCH v2 3/4] signal/x86: Move restore_saved_sigmask() NIIBE Yutaka
2018-03-22 1:44 ` NIIBE Yutaka [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=20180322014413.24099-5-gniibe@fsij.org \
--to=gniibe@fsij.org \
--cc=linux-kernel@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 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®