From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: entry: always restore x0 from the stack on syscall return
Date: Wed, 19 Aug 2015 17:23:59 +0100 [thread overview]
Message-ID: <20150819162359.GA10297@arm.com> (raw)
In-Reply-To: <20150819160320.GI24062@e104818-lin.cambridge.arm.com>
On Wed, Aug 19, 2015 at 05:03:20PM +0100, Catalin Marinas wrote:
> On Wed, Aug 19, 2015 at 04:09:49PM +0100, Will Deacon wrote:
> > @@ -613,13 +609,14 @@ ENDPROC(cpu_switch_to)
> > */
> > ret_fast_syscall:
> > disable_irq // disable interrupts
> > + str x0, [sp, #S_X0] // returned x0
> > ldr x1, [tsk, #TI_FLAGS] // re-check for syscall tracing
> > and x2, x1, #_TIF_SYSCALL_WORK
> > cbnz x2, ret_fast_syscall_trace
> > and x2, x1, #_TIF_WORK_MASK
> > - cbnz x2, fast_work_pending
> > + cbnz x2, work_pending
> > enable_step_tsk x1, x2
> > - kernel_exit 0, ret = 1
> > + kernel_exit 0
> > ret_fast_syscall_trace:
> > enable_irq // enable interrupts
> > b __sys_trace_return
>
> There is another str x0 in __sys_trace_return which I think we could
> remove.
Hmm, I don't think we can remove that. It's needed on the slowpath to
update the pt_regs with either -ENOSYS (for __ni_sys_trace) or the
syscall return value from the blr in __sys_trace.
What we can do instead is change the branch above to branch to
__sys_trace_return_skipped. Patch below.
Will
--->8
diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S
index 2a5e64ccc991..088322ff1ba0 100644
--- a/arch/arm64/kernel/entry.S
+++ b/arch/arm64/kernel/entry.S
@@ -619,7 +619,7 @@ ret_fast_syscall:
kernel_exit 0
ret_fast_syscall_trace:
enable_irq // enable interrupts
- b __sys_trace_return
+ b __sys_trace_return_skipped // we already saved x0
/*
* Ok, we need to do extra processing, enter the slow path.
next prev parent reply other threads:[~2015-08-19 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 15:09 [PATCH] arm64: entry: always restore x0 from the stack on syscall return Will Deacon
2015-08-19 16:03 ` Catalin Marinas
2015-08-19 16:23 ` Will Deacon [this message]
2015-08-19 16:35 ` Catalin Marinas
2015-08-19 16:56 ` Will Deacon
2015-08-20 8:42 ` Hanjun Guo
2015-08-20 10:51 ` Will Deacon
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=20150819162359.GA10297@arm.com \
--to=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).