From: Al Viro <viro@ZenIV.linux.org.uk>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc64: exit_group should kill register windows just like plain exit.
Date: Mon, 03 Dec 2012 19:35:58 +0000 [thread overview]
Message-ID: <20121203193558.GP4939@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20121203.143049.901444782954231849.davem@davemloft.net>
On Mon, Dec 03, 2012 at 02:30:49PM -0500, David Miller wrote:
>
> Reported-by: Al Viro <viro@ZenIV.linux.org.uk>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> ---
> arch/sparc/kernel/sys32.S | 2 +-
> arch/sparc/kernel/syscalls.S | 14 ++++++++++++--
> arch/sparc/kernel/systbls_64.S | 2 +-
> 3 files changed, 14 insertions(+), 4 deletions(-)
>
> diff --git a/arch/sparc/kernel/sys32.S b/arch/sparc/kernel/sys32.S
> index 44025f4..8475a47 100644
> --- a/arch/sparc/kernel/sys32.S
> +++ b/arch/sparc/kernel/sys32.S
> @@ -47,7 +47,7 @@ STUB: sra REG1, 0, REG1; \
> sra REG4, 0, REG4
>
> SIGN1(sys32_exit, sparc_exit, %o0)
> -SIGN1(sys32_exit_group, sys_exit_group, %o0)
> +SIGN1(sys32_exit_group, sparc_exit_group, %o0)
No need of that part, really. sys_exit_group() will have its argument
(int) normalized all by itself. The same goes for sys_exit(), so
sys32_exit is also pointless; just have sparc_exit/sparc_exit_group in
32bit syscall table, same as you do in 64bit one...
next prev parent reply other threads:[~2012-12-03 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 19:30 [PATCH] sparc64: exit_group should kill register windows just like plain exit David Miller
2012-12-03 19:35 ` Al Viro [this message]
2012-12-03 19:37 ` David Miller
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=20121203193558.GP4939@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=sparclinux@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.