From: ebiederm@xmission.com (Eric W. Biederman)
To: "Albert Cahalan" <acahalan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: wait4/waitpid/waitid oddness
Date: Fri, 07 Apr 2006 12:23:38 -0600 [thread overview]
Message-ID: <m1acaxnt1x.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <787b0d920604052038i3a75bdb6ic0818d93805b881b@mail.gmail.com> (Albert Cahalan's message of "Wed, 5 Apr 2006 23:38:20 -0400")
"Albert Cahalan" <acahalan@gmail.com> writes:
> The kernel prohibits:
>
> 1. WNOHANG on waitpid/wait4
Not 2.6.17-rc1, and not for a lot of earlier kernels.
At least not on ingress, and just skimming the code
I can't see any deeper checks that would prevent this.
> 2. __WALL on waitid
>
> Why? I need both at once.
Which kernel is failing, and how?
Eric
next prev parent reply other threads:[~2006-04-07 18:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 3:38 wait4/waitpid/waitid oddness Albert Cahalan
2006-04-07 2:09 ` Joshua Hudson
2006-04-07 5:38 ` Kyle Moffett
2006-04-07 6:40 ` Joshua Hudson
2006-04-07 6:50 ` Neil Brown
2006-04-07 7:09 ` Joshua Hudson
2006-04-07 18:23 ` Eric W. Biederman [this message]
2006-04-07 18:58 ` Joshua Hudson
2006-04-07 19:19 ` Eric W. Biederman
2006-04-07 19:24 ` Joshua Hudson
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=m1acaxnt1x.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=acahalan@gmail.com \
--cc=linux-kernel@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.