From: Arnd Bergmann <arnd@arndb.de>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: compat syscall args
Date: Tue, 1 Jun 2004 15:03:16 +0200 [thread overview]
Message-ID: <200406011503.16323.arnd@arndb.de> (raw)
In-Reply-To: <20040529123155.5ca76207.davem@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
On Saturday 29 May 2004 21:31, David S. Miller wrote:
> As it turns out we're taking care of this already via stubs
> in arch/sparc64/kernel/sys32.S, I just need to add them for
> select and futex.
Ah, thanks for solving this mystery.
select and futex may not be the only ones that need to be fixed
for sparc64. I grepped through the list of syscalls that you
call without a sys32.S wrapper and found these that take at least
five arguments:
compat_sys_io_getevents, compat_sys_mount, sys_fsetxattr,
sys_setsockopt, sys_llseek, sys_mremap, sys_remap_file_pages,
sys_setxattr, sys_lsetxattr, sys_fsetxattr, sys32_fadvise64,
sys32_fadvise64_64, sys32_ipc, sys32_mremap, sys32_pciconfig_read,
sys32_pciconfig_write, sys32_prctl, sys32_pread64, sys32_pwrite64,
sys32_rt_sigaction
I did not check which ones are safe anyway, but you probably
want to go through that list.
Arnd <><
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-01 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 19:23 compat syscall args David S. Miller
2004-05-29 19:31 ` David S. Miller
2004-06-01 13:03 ` Arnd Bergmann [this message]
2004-06-01 5:06 ` Stephen Rothwell
2004-06-01 9:07 ` Arnd Bergmann
2004-06-01 9:24 ` David S. Miller
[not found] <21hGW-h5-5@gated-at.bofh.it>
[not found] ` <229Hi-B1-11@gated-at.bofh.it>
[not found] ` <22drH-3Bc-47@gated-at.bofh.it>
[not found] ` <22dL7-3O8-39@gated-at.bofh.it>
2004-06-01 13:07 ` Andi Kleen
2004-06-01 17:04 ` Anton Blanchard
2004-06-01 21:28 ` David S. 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=200406011503.16323.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=davem@redhat.com \
--cc=linux-kernel@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