From: Greg Ungerer <gerg@uclinux.org>
To: linux-m68k@vger.kernel.org
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH] m68k: use conventional function parameters for do_sigreturn
Date: Mon, 1 Feb 2016 14:33:26 +1000 [thread overview]
Message-ID: <56AEE016.3050102@uclinux.org> (raw)
In-Reply-To: <1453183018-11722-1-git-send-email-gerg@uclinux.org>
Anyone have any thoughts or comments on this?
On 19/01/16 15:56, Greg Ungerer wrote:
> Create conventional stack parameters for the calls to do_sigreturn and
> do_rt_sigreturn. The current C code for do_sigreturn and do_rt_sigreturn
> dig into the stack to create local pointers to the saved switch stack
> and the pt_regs structs.
>
> Using conventional stack parameters passed to these functions means the
> code here does not need to know the exact details of how the underlying
> entry handler layed these structs out on the stack.
>
> The motivation for this change is a problem with non-MMU targets that
> have broken signal return paths on newer versions of gcc. It appears as
> though aliasing of the regs and switch stack pointers, caused by their
> construction from pointers derived from the dummy long function parameter,
> is resulting in the gcc optimizer removing what it thinks is useless
> updates to the regs fields. Large parts of restore_sigcontext() and
> mangle_kernel_stack() functions get optimized out. Of course this results
> in non-functional code causing kernel oops. This problem has been observed
> with gcc version 5.2 and 5.3, and probably exists in earlier versions as
> well.
>
> The resulting code after this change is a few bytes larger (due to the
> overhead of creating the stack args and their tear down). Not being hot
> paths I don't think this is too much of a problem here.
>
> This change has been compile tested on all defconfigs, and run tested on
> Atari (through aranym), ColdFire with MMU (M5407EVB) and ColdFire with
> no-MMU (QEMU and M5208EVB).
>
> Signed-off-by: Greg Ungerer <gerg@uclinux.org>
> ---
> arch/m68k/kernel/entry.S | 6 ++++++
> arch/m68k/kernel/signal.c | 8 ++------
> 2 files changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/arch/m68k/kernel/entry.S b/arch/m68k/kernel/entry.S
> index b54ac7a..97cd3ea 100644
> --- a/arch/m68k/kernel/entry.S
> +++ b/arch/m68k/kernel/entry.S
> @@ -71,13 +71,19 @@ ENTRY(__sys_vfork)
>
> ENTRY(sys_sigreturn)
> SAVE_SWITCH_STACK
> + movel %sp,%sp@- | switch_stack pointer
> + pea %sp@(SWITCH_STACK_SIZE+4) | pt_regs pointer
> jbsr do_sigreturn
> + addql #8,%sp
> RESTORE_SWITCH_STACK
> rts
>
> ENTRY(sys_rt_sigreturn)
> SAVE_SWITCH_STACK
> + movel %sp,%sp@- | switch_stack pointer
> + pea %sp@(SWITCH_STACK_SIZE+4) | pt_regs pointer
> jbsr do_rt_sigreturn
> + addql #8,%sp
> RESTORE_SWITCH_STACK
> rts
>
> diff --git a/arch/m68k/kernel/signal.c b/arch/m68k/kernel/signal.c
> index af1c4f3..2dcee3a 100644
> --- a/arch/m68k/kernel/signal.c
> +++ b/arch/m68k/kernel/signal.c
> @@ -737,10 +737,8 @@ badframe:
> return 1;
> }
>
> -asmlinkage int do_sigreturn(unsigned long __unused)
> +asmlinkage int do_sigreturn(struct pt_regs *regs, struct switch_stack *sw)
> {
> - struct switch_stack *sw = (struct switch_stack *) &__unused;
> - struct pt_regs *regs = (struct pt_regs *) (sw + 1);
> unsigned long usp = rdusp();
> struct sigframe __user *frame = (struct sigframe __user *)(usp - 4);
> sigset_t set;
> @@ -764,10 +762,8 @@ badframe:
> return 0;
> }
>
> -asmlinkage int do_rt_sigreturn(unsigned long __unused)
> +asmlinkage int do_rt_sigreturn(struct pt_regs *regs, struct switch_stack *sw)
> {
> - struct switch_stack *sw = (struct switch_stack *) &__unused;
> - struct pt_regs *regs = (struct pt_regs *) (sw + 1);
> unsigned long usp = rdusp();
> struct rt_sigframe __user *frame = (struct rt_sigframe __user *)(usp - 4);
> sigset_t set;
>
next prev parent reply other threads:[~2016-02-01 4:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 5:56 [PATCH] m68k: use conventional function parameters for do_sigreturn Greg Ungerer
2016-02-01 4:33 ` Greg Ungerer [this message]
2016-02-01 18:39 ` Andreas Schwab
2016-02-01 23:59 ` Greg Ungerer
2016-02-02 19:25 ` Andreas Schwab
2016-02-03 4:14 ` Greg Ungerer
2016-02-08 23:31 ` Andreas Schwab
2016-02-09 0:21 ` Greg Ungerer
2016-02-09 9:48 ` Andreas Schwab
2016-02-09 13:05 ` Greg Ungerer
2016-02-09 13:17 ` Andreas Schwab
2016-02-09 14:01 ` Philippe De Muyter
2016-02-09 14:36 ` Andreas Schwab
2016-02-09 15:26 ` Philippe De Muyter
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=56AEE016.3050102@uclinux.org \
--to=gerg@uclinux.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@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 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.