From mboxrd@z Thu Jan 1 00:00:00 1970 From: josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org Subject: Re: [PATCH] clone.2: Document that clone silently ignores CLONE_PID and CLONE_STOPPED Date: Mon, 2 Mar 2015 08:40:50 -0800 Message-ID: <20150302164050.GA29046@cloud> References: <20150227004118.GA15530@jtriplet-mobl1> <54F011E4.1020502@gmail.com> <20150227163157.GA10309@cloud> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-man-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Michael Kerrisk (man-pages)" Cc: linux-man List-Id: linux-man@vger.kernel.org On Mon, Mar 02, 2015 at 05:27:38PM +0100, Michael Kerrisk (man-pages) wrote: > On 27 February 2015 at 17:31, 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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html