From: Mike Frysinger <vapier@gentoo.org>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: "James E.J. Bottomley" <jejb@parisc-linux.org>,
Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] parisc: fix a bug when syscall number of tracee is __NR_Linux_syscalls
Date: Tue, 26 Apr 2016 22:45:11 -0400 [thread overview]
Message-ID: <20160427024511.GA5369@vapier.lan> (raw)
In-Reply-To: <20160427015611.GA23316@altlinux.org>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
On 27 Apr 2016 04:56, Dmitry V. Levin wrote:
> Do not load one entry beyond the end of the syscall table when the
> syscall number of a traced process equals to __NR_Linux_syscalls.
> Similar bug with regular processes was fixed by commit 3bb457af4fa8
> ("[PARISC] Fix bug when syscall nr is __NR_Linux_syscalls").
>
> This bug was found by strace test suite.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
> ---
> arch/parisc/kernel/syscall.S | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/parisc/kernel/syscall.S b/arch/parisc/kernel/syscall.S
> index c976ebf..57b4836 100644
> --- a/arch/parisc/kernel/syscall.S
> +++ b/arch/parisc/kernel/syscall.S
> @@ -344,7 +344,7 @@ tracesys_next:
> #endif
>
> cmpib,COND(=),n -1,%r20,tracesys_exit /* seccomp may have returned -1 */
> - comiclr,>>= __NR_Linux_syscalls, %r20, %r0
> + comiclr,>> __NR_Linux_syscalls, %r20, %r0
> b,n .Ltracesys_nosys
>
> LDREGX %r20(%r19), %r19
i've deployd your fix to hake, so feel free to give the tests another
run to try and crash the box :).
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-27 2:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 1:56 [PATCH] parisc: fix a bug when syscall number of tracee is __NR_Linux_syscalls Dmitry V. Levin
2016-04-27 2:45 ` Mike Frysinger [this message]
2016-04-27 3:28 ` Dmitry V. Levin
2016-04-27 19:23 ` Helge Deller
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=20160427024511.GA5369@vapier.lan \
--to=vapier@gentoo.org \
--cc=deller@gmx.de \
--cc=jejb@parisc-linux.org \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@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;
as well as URLs for NNTP newsgroup(s).