All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: sparclinux@vger.kernel.org
Subject: sparc: sys32.S incorrect compat-layer splice() system call
Date: Wed, 19 Aug 2009 02:56:23 +0000	[thread overview]
Message-ID: <20090819025623.GA11677@Krystal> (raw)

Hi David,

I just installed a shiny (old) Sparc64 machine, trying to get LTTng to
run on it (2.6.30 kernel), and noticed this problem when extracting the
buffers: lttd (the daemon) causes faults in __copy_from_user() within
splice().

lttd is compiled as a 32-bits process on my system. The kernel is
64-bits kernel.

I think arch/sparc/kernel/sys32.S has an incorrect splice definition:

SIGN2(sys32_splice, sys_splice, %o0, %o1)

The splice() prototype looks like :

       long splice(int fd_in, loff_t *off_in, int fd_out,
                   loff_t *off_out, size_t len, unsigned int flags);

So I think we should have :

SIGN2(sys32_splice, sys_splice, %o0, %o2)

instead, am I correct ?


BTW, I can't figure out why we have %o5 in :

SIGN2(sys32_sync_file_range, compat_sync_file_range, %o0, %o5)

which takes only 4 arguments:

       int sync_file_range(int fd, off64_t offset, off64_t nbytes,
                  unsigned int flags);

maybe it has something to do with the return value ? Anyway it should
not hurt if it is unused.


I provide the patch for splice() below.

With this patch applied, I have been able to gather a trace with LTTng
and view it in LTTV. Next steps for LTTng support on sparc64 are to add
the syscall and trap instrumentation.

Thanks,

Mathieu


sparc: sys32.S incorrect compat-layer splice() system call

I think arch/sparc/kernel/sys32.S has an incorrect splice definition:

SIGN2(sys32_splice, sys_splice, %o0, %o1)

The splice() prototype looks like :

       long splice(int fd_in, loff_t *off_in, int fd_out,
                   loff_t *off_out, size_t len, unsigned int flags);

So I think we should have :

SIGN2(sys32_splice, sys_splice, %o0, %o2)

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
CC: "David S. Miller" <davem@caip.rutgers.edu>
CC: Jakub Jelinek <jj@ultra.linux.cz>
---
 arch/sparc/kernel/sys32.S |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: linux-2.6-lttng/arch/sparc/kernel/sys32.S
=================================--- linux-2.6-lttng.orig/arch/sparc/kernel/sys32.S	2009-08-18 21:21:20.000000000 -0400
+++ linux-2.6-lttng/arch/sparc/kernel/sys32.S	2009-08-18 21:56:47.000000000 -0400
@@ -134,7 +134,7 @@ SIGN1(sys32_getpeername, sys_getpeername
 SIGN1(sys32_getsockname, sys_getsockname, %o0)
 SIGN2(sys32_ioprio_get, sys_ioprio_get, %o0, %o1)
 SIGN3(sys32_ioprio_set, sys_ioprio_set, %o0, %o1, %o2)
-SIGN2(sys32_splice, sys_splice, %o0, %o1)
+SIGN2(sys32_splice, sys_splice, %o0, %o2)
 SIGN2(sys32_sync_file_range, compat_sync_file_range, %o0, %o5)
 SIGN2(sys32_tee, sys_tee, %o0, %o1)
 SIGN1(sys32_vmsplice, compat_sys_vmsplice, %o0)

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

             reply	other threads:[~2009-08-19  2:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19  2:56 Mathieu Desnoyers [this message]
2009-08-19  3:16 ` sparc: sys32.S incorrect compat-layer splice() system call David Miller
2009-08-19  3:40 ` Mathieu Desnoyers
2009-08-19  4:21 ` 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=20090819025623.GA11677@Krystal \
    --to=mathieu.desnoyers@polymtl.ca \
    --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.