From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel@vger.kernel.org, paulus@samba.org, anton@samba.org,
davem@davemloft.net, ralf@linux-mips.org, tony.luck@intel.com,
ak@suse.de, willy@debian.org, schwidefsky@de.ibm.com
Subject: Re: [PATCH] Consolidate compat_sys_waitid
Date: Fri, 18 Feb 2005 16:22:29 +1100 [thread overview]
Message-ID: <20050218162229.63d69935.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20050215184307.GQ29917@parcelfarce.linux.theplanet.co.uk>
On Tue, 15 Feb 2005 18:43:07 +0000 Matthew Wilcox <matthew@wil.cx> wrote:
>
> On Tue, Feb 15, 2005 at 02:01:49PM +1100, Stephen Rothwell wrote:
>
> > +asmlinkage long compat_sys_waitid(u32 which, u32 pid,
> > + struct compat_siginfo __user *uinfo, u32 options,
> > + struct compat_rusage __user *uru)
>
> Some subtle differences which I feel incompetent to diagnose ... ours
> looks like:
>
> asmlinkage int compat_sys_waitid(int which, pid_t pid,
> compat_siginfo_t __user *infop, int options,
> struct compat_rusage __user *ru)
They are u32 in my version because we decided that the kernel zero extends
the compat syscall parameters.
> Other than variable names, we're identical to this point:
>
> /* Tell copy_siginfo_to_user that it was __SI_CHLD */
> ksiginfo.si_code |= __SI_CHLD;
>
> if (compat_copy_siginfo_to_user(infop, &ksiginfo) != 0)
Every other relevant architecture has copy_siginfo_to_user32 which returns
0/-EFAULT. And it is declared in linux/compat.h. I like your name
better, but that is a different patch.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
next prev parent reply other threads:[~2005-02-18 5:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 3:01 Stephen Rothwell
2005-02-15 9:51 ` Andi Kleen
2005-02-15 11:06 ` Stephen Rothwell
2005-02-15 11:10 ` Andi Kleen
2005-02-15 18:37 ` David S. Miller
2005-02-15 18:43 ` Matthew Wilcox
2005-02-15 19:23 ` Andi Kleen
2005-02-15 19:27 ` Al Viro
2005-02-18 5:22 ` Stephen Rothwell [this message]
2005-02-15 19:33 ` Daniel Jacobowitz
2005-02-16 0:06 ` Paul Mackerras
2005-02-15 18:09 Luck, Tony
2005-03-07 1:08 Stephen Rothwell
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=20050218162229.63d69935.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ak@suse.de \
--cc=anton@samba.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=schwidefsky@de.ibm.com \
--cc=tony.luck@intel.com \
--cc=willy@debian.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
all inboxes | Powered by JetHome®