From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thiago Macieira Subject: Re: [PATCH v2 5/7] clone4: Add a CLONE_AUTOREAP flag to automatically reap the child process Date: Fri, 20 Mar 2015 11:46:33 -0700 Message-ID: <1766646.jusoNDOCPE@tjmaciei-mobl4> References: <20150315233439.GA31890@thin> <20150320181404.GA26343@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: <20150320181404.GA26343@redhat.com> Sender: linux-kernel-owner@vger.kernel.org To: Oleg Nesterov Cc: Josh Triplett , Al Viro , Andrew Morton , Andy Lutomirski , Ingo Molnar , Kees Cook , "Paul E. McKenney" , "H. Peter Anvin" , Rik van Riel , Thomas Gleixner , Michael Kerrisk , linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org, x86@kernel.org List-Id: linux-api@vger.kernel.org On Friday 20 March 2015 19:14:04 Oleg Nesterov wrote: > Also. I forgot that the kernel always resets ->exit_signal to SIGCHLD on > exec or reparenting. Reparenting is probably fine. But what about exec? > Should it keep ->exit_signal == 0 if "autoreap" ? I think it should not, to > avoid the strange special case. Not delivering any signal was the objective of this patch series, so yes exit_signal == 0 should survive an exec and even re-exec. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center