From: Matthew Wilcox <matthew@wil.cx>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: LKML <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: Tue, 15 Feb 2005 18:43:07 +0000 [thread overview]
Message-ID: <20050215184307.GQ29917@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20050215140149.0b06c96b.sfr@canb.auug.org.au>
On Tue, Feb 15, 2005 at 02:01:49PM +1100, Stephen Rothwell wrote:
> Parisc seemed to assume th existance of compat_sys_waitid.
PA-RISC already has a compat_sys_waitid ;-P
The reason it isn't in Linus' tree yet is that it depends on the
is_compat_task() predicate which Andi vetoed out of Andrew's tree.
As a result, I haven't been able to merge any of the compat stuff
sitting in the PA tree. A few more voices in favour of reintroducing
is_compat_task() would help.
> @@ -413,6 +414,36 @@ compat_sys_wait4(compat_pid_t pid, compa
> }
> }
>
> +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)
> + BUG_ON(info.si_code & __SI_MASK);
> + info.si_code |= __SI_CHLD;
> + return copy_siginfo_to_user32(uinfo, &info);
> +}
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)
return -EFAULT;
return 0;
}
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2005-02-15 18:45 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 [this message]
2005-02-15 19:23 ` Andi Kleen
2005-02-15 19:27 ` Al Viro
2005-02-18 5:22 ` Stephen Rothwell
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=20050215184307.GQ29917@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=ak@suse.de \
--cc=anton@samba.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=schwidefsky@de.ibm.com \
--cc=sfr@canb.auug.org.au \
--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®