From: Andreas Schwab <schwab@linux-m68k.org>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: "Jason A . Donenfeld" <Jason@zx2c4.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] powerpc/32: fix syscall wrappers with 64-bit arguments of unaligned register-pairs
Date: Sun, 30 Oct 2022 18:03:34 +0100 [thread overview]
Message-ID: <878rkxgs61.fsf@igel.home> (raw)
In-Reply-To: <20221012035335.866440-1-npiggin@gmail.com> (Nicholas Piggin's message of "Wed, 12 Oct 2022 13:53:34 +1000")
On Okt 12 2022, Nicholas Piggin wrote:
> diff --git a/arch/powerpc/kernel/syscalls/syscall.tbl b/arch/powerpc/kernel/syscalls/syscall.tbl
> index 2bca64f96164..e9e0df4f9a61 100644
> --- a/arch/powerpc/kernel/syscalls/syscall.tbl
> +++ b/arch/powerpc/kernel/syscalls/syscall.tbl
> @@ -228,8 +228,10 @@
> 176 64 rt_sigtimedwait sys_rt_sigtimedwait
> 177 nospu rt_sigqueueinfo sys_rt_sigqueueinfo compat_sys_rt_sigqueueinfo
> 178 nospu rt_sigsuspend sys_rt_sigsuspend compat_sys_rt_sigsuspend
> -179 common pread64 sys_pread64 compat_sys_ppc_pread64
> -180 common pwrite64 sys_pwrite64 compat_sys_ppc_pwrite64
> +179 32 pread64 sys_ppc_pread64 compat_sys_ppc_pread64
> +179 64 pread64 sys_pread64
> +180 32 pwrite64 sys_ppc_pwrite64 compat_sys_ppc_pwrite64
> +180 64 pwrite64 sys_pwrite64
Doesn't that lack entries for SPU? Likewise for all other former common
syscalls in this patch.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2022-10-30 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 3:53 [PATCH 1/2] powerpc/32: fix syscall wrappers with 64-bit arguments of unaligned register-pairs Nicholas Piggin
2022-10-12 3:53 ` [PATCH 2/2] powerpc: move sync_file_range2 compat definition Nicholas Piggin
2022-10-12 10:21 ` Arnd Bergmann
2022-10-12 7:56 ` [PATCH 1/2] powerpc/32: fix syscall wrappers with 64-bit arguments of unaligned register-pairs Andrew Donnellan
2022-10-12 10:15 ` Arnd Bergmann
2022-10-14 23:21 ` (subset) " Michael Ellerman
2022-10-30 17:03 ` Andreas Schwab [this message]
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=878rkxgs61.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=Jason@zx2c4.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
/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).