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

* David Miller (davem@davemloft.net) wrote:
> From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
> Date: Tue, 18 Aug 2009 22:56:23 -0400
> 
> > 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 ?
> 
> Indeed, that's correct, thanks for your fix.  I'll apply it.
> 
> > 
> > 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.
> 
> It takes 4 arguments, but they are passed in 6 registers.  Each
> off64_t is passed in two 32-bit register parts.
> 

Thanks for the clarification. So the %o5 is there to sign-extend
"unsigned int flags" ?

Mathieu

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

  parent reply	other threads:[~2009-08-19  3:40 UTC|newest]

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