From: Andi Kleen <ak@muc.de>
To: Roland McGrath <roland@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] waitid system call
Date: Mon, 16 Aug 2004 02:03:37 +0200 [thread overview]
Message-ID: <m3smaoc5k6.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <2tCiy-8pK-13@gated-at.bofh.it> (Roland McGrath's message of "Mon, 16 Aug 2004 01:10:06 +0200")
Roland McGrath <roland@redhat.com> writes:
Are you sure you converted the new _rusage member properly
in the 64->32bit siginfo converter? struct rusage uses long.
> +asmlinkage long sys32_waitid(int which, compat_pid_t pid,
> + siginfo_t32 __user *uinfo, int options)
> +{
> + siginfo_t info;
> + long ret;
> + mm_segment_t old_fs = get_fs();
> +
> + info.si_signo = 0;
> + set_fs (KERNEL_DS);
> + ret = sys_waitid(which, pid, (siginfo_t __user *) &info, options);
> + set_fs (old_fs);
Better use compat_alloc_user_space() for this. Otherwise it won't
work for UML/x86-64. Also that will make it easier to port to other
architectures.
+ /* 1 if group stopped since last SIGCONT, -1 if SIGCONT since report */
+ int stop_state;
Can't this be merged into some other field? No need to waste memory
unnecessarily.
-Andi
next parent reply other threads:[~2004-08-16 0:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2tCiy-8pK-13@gated-at.bofh.it>
2004-08-16 0:03 ` Andi Kleen [this message]
2004-08-16 2:10 ` [PATCH] waitid system call Roland McGrath
2004-08-15 23:03 Roland McGrath
2004-08-16 5:40 ` Roland McGrath
2004-08-16 17:15 ` Michael Kerrisk
2004-08-16 21:12 ` Roland McGrath
2004-08-19 17:20 ` Michael Kerrisk
2004-08-19 20:53 ` Roland McGrath
2004-08-20 6:00 ` Michael Kerrisk
2004-08-20 9:02 ` Michael Kerrisk
2004-08-20 20:04 ` Roland McGrath
2004-08-24 11:51 ` Michael Kerrisk
2004-08-31 6:04 ` Roland McGrath
2004-08-31 6:26 ` Jakub Jelinek
2004-08-31 6:37 ` Roland McGrath
2004-08-31 6:40 ` Andrew Morton
2004-08-31 15:53 ` Bill Davidsen
2004-08-31 18:26 ` Linus Torvalds
2004-08-31 23:51 ` Roland McGrath
2004-09-01 11:31 ` Michael Kerrisk
2004-08-31 7:22 ` Michael Kerrisk
2004-08-22 8:53 ` Tonnerre
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=m3smaoc5k6.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
/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.