Re: wait4/waitpid/waitid oddness

On 4/7/06, Eric W. Biederman <[email protected]> wrote:
> "Albert Cahalan" <[email protected]> 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?

LKNL 2.6.16.1 has this check. Haven't checked any others.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: wait4/waitpid/waitid oddness
    • From: [email protected] (Eric W. Biederman)

• References:
  • wait4/waitpid/waitid oddness
    • From: "Albert Cahalan" <[email protected]>
  • Re: wait4/waitpid/waitid oddness
    • From: [email protected] (Eric W. Biederman)

• Prev by Date: Re: [RFC] packet/socket owner match (fireflier) using skfilter
• Next by Date: Fwd: [PATCH] Add a /proc/self/exedir link
• Previous by thread: Re: wait4/waitpid/waitid oddness
• Next by thread: Re: wait4/waitpid/waitid oddness
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]