From: evgsyr@gmail.com (Eugene Syromyatnikov)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: Call syscall_trace_exit even when system call skipped
Date: Mon, 8 Oct 2018 13:00:52 +0200 [thread overview]
Message-ID: <20181008110047.GA3426@asgard.redhat.com> (raw)
In-Reply-To: <20180203152112.2449-1-T.E.Baldwin99@members.leeds.ac.uk>
From: Timothy E Baldwin <T.E.Baldwin99@members.leeds.ac.uk>
On at least x86 and ARM64, and as documented in the ptrace man page
a skipped system call will still cause a syscall exit ptrace stop.
Previous to this commit 32-bit ARM did not, resulting in strace
being confused when seccomp skips system calls.
This change also impacts programs that use ptrace to skip system calls.
Fixes: ad75b51459ae ("ARM: 7579/1: arch/allow a scno of -1 to not cause a SIGILL")
Signed-off-by: Timothy E Baldwin <T.E.Baldwin99@members.leeds.ac.uk>
Signed-off-by: Eugene Syromyatnikov <evgsyr@gmail.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
Tested-by: Kees Cook <keescook@chromium.org>
Tested-by: Eugene Syromyatnikov <evgsyr@gmail.com>
---
KernelVersion: 4.19-rc7
diff --git a/arch/arm/kernel/entry-common.S b/arch/arm/kernel/entry-common.S
index 746565a..0465d65 100644
--- a/arch/arm/kernel/entry-common.S
+++ b/arch/arm/kernel/entry-common.S
@@ -296,16 +296,15 @@ __sys_trace:
cmp scno, #-1 @ skip the syscall?
bne 2b
add sp, sp, #S_OFF @ restore stack
- b ret_slow_syscall
-__sys_trace_return:
- str r0, [sp, #S_R0 + S_OFF]! @ save returned r0
+__sys_trace_return_nosave:
+ enable_irq_notrace
mov r0, sp
bl syscall_trace_exit
b ret_slow_syscall
-__sys_trace_return_nosave:
- enable_irq_notrace
+__sys_trace_return:
+ str r0, [sp, #S_R0 + S_OFF]! @ save returned r0
mov r0, sp
bl syscall_trace_exit
b ret_slow_syscall
--
2.1.4
next prev parent reply other threads:[~2018-10-08 11:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 15:21 [PATCH] ARM: Call syscall_trace_exit even when system call skipped Timothy E Baldwin
2018-03-13 23:58 ` Dmitry V. Levin
2018-03-15 0:44 ` Kees Cook
2018-03-15 10:38 ` T.E.Baldwin99 at members.leeds.ac.uk
2018-03-15 20:14 ` Kees Cook
2018-09-29 23:03 ` Eugene Syromyatnikov
2018-10-08 7:11 ` Eugene Syromyatnikov
2018-10-08 9:58 ` Vladimir Murzin
2018-10-08 11:00 ` Eugene Syromyatnikov [this message]
2018-10-08 18:08 ` Kees Cook
2018-10-08 18:13 ` Russell King - ARM Linux
2018-10-08 18:33 ` Eugene Syromyatnikov
2018-10-08 18:26 ` Eugene Syromyatnikov
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=20181008110047.GA3426@asgard.redhat.com \
--to=evgsyr@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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.