Re: [PATCH] clone.2: Document that clone silently ignores CLONE_PID and CLONE_STOPPED

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Mar 02, 2015 at 05:27:38PM +0100, Michael Kerrisk (man-pages) wrote:
> On 27 February 2015 at 17:31,  <josh@xxxxxxxxxxxxxxxx> wrote:
> > On Fri, Feb 27, 2015 at 07:42:44AM +0100, Michael Kerrisk (man-pages) wrote:
> >> On 02/27/2015 01:41 AM, Josh Triplett wrote:
> >> > Normally, system calls return EINVAL for flags they don't support.
> >> > Explicitly document that clone does *not* produce an error for these two
> >> > obsolete flags.
> >>
> >> Thanks, Josh! Applied.
> >
> > Doesn't appear to be in the current git repository.
> 
> Pushed now, Josh. (I needed to get another release out of the way first.)

No problem; thanks for the update.

Related issue: the errors section of clone.2 claims it'll return EPERM
for CLONE_PID by something other than PID 0 (meaning, outside the
kernel), but that doesn't actually happen.  Should that be dropped?  (I
can send a patch if so.)

- Josh Triplett
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux