From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [PATCH v2] Implement close-on-fork Date: Fri, 15 May 2020 17:03:42 +0100 Message-ID: <20200515160342.GE23230@ZenIV.linux.org.uk> References: <20200515152321.9280-1-nate.karstens@garmin.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20200515152321.9280-1-nate.karstens@garmin.com> Sender: linux-kernel-owner@vger.kernel.org To: Nate Karstens Cc: Jeff Layton , "J. Bruce Fields" , Arnd Bergmann , Richard Henderson , Ivan Kokshaysky , Matt Turner , "James E.J. Bottomley" , Helge Deller , "David S. Miller" , Jakub Kicinski , Eric Dumazet , David Laight , linux-fsdevel@vger.kernel.org, linux-arch@vger.kernel.org, linux-alpha@vger.kernel.org, linux-parisc@vger.kernel.org, sparclinux@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Changli Gao List-Id: linux-arch.vger.kernel.org On Fri, May 15, 2020 at 10:23:17AM -0500, Nate Karstens wrote: > This functionality was approved by the Austin Common Standards > Revision Group for inclusion in the next revision of the POSIX > standard (see issue 1318 in the Austin Group Defect Tracker). It penalizes every call of fork() in the system (as well as adds an extra dirtied cacheline on each socket()/open()/etc.), adds memory footprint and complicates the API. All of that - to deal with rather uncommon problem that already has a portable solution. As for the Austin Group, the only authority it has ever had derives from consensus between existing Unices. "Solaris does it, Linux and *BSD do not" translates into "Austin Group is welcome to take a hike". BTW, contrary to the lovely bit of misrepresentation in that thread of theirs (" suggests that" != "someone's comment under LWN article says it _appears_ that"), none of *BSD do it. IMO it's a bad idea. NAKed-by: Al Viro From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49414 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1726239AbgEOQEf (ORCPT ); Fri, 15 May 2020 12:04:35 -0400 Date: Fri, 15 May 2020 17:03:42 +0100 From: Al Viro Subject: Re: [PATCH v2] Implement close-on-fork Message-ID: <20200515160342.GE23230@ZenIV.linux.org.uk> References: <20200515152321.9280-1-nate.karstens@garmin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200515152321.9280-1-nate.karstens@garmin.com> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Nate Karstens Cc: Jeff Layton , "J. Bruce Fields" , Arnd Bergmann , Richard Henderson , Ivan Kokshaysky , Matt Turner , "James E.J. Bottomley" , Helge Deller , "David S. Miller" , Jakub Kicinski , Eric Dumazet , David Laight , linux-fsdevel@vger.kernel.org, linux-arch@vger.kernel.org, linux-alpha@vger.kernel.org, linux-parisc@vger.kernel.org, sparclinux@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Changli Gao Message-ID: <20200515160342.4WE2AUaCE5iKLeC_bBSPfST8bR6PHXxddElPnj1pJEE@z> On Fri, May 15, 2020 at 10:23:17AM -0500, Nate Karstens wrote: > This functionality was approved by the Austin Common Standards > Revision Group for inclusion in the next revision of the POSIX > standard (see issue 1318 in the Austin Group Defect Tracker). It penalizes every call of fork() in the system (as well as adds an extra dirtied cacheline on each socket()/open()/etc.), adds memory footprint and complicates the API. All of that - to deal with rather uncommon problem that already has a portable solution. As for the Austin Group, the only authority it has ever had derives from consensus between existing Unices. "Solaris does it, Linux and *BSD do not" translates into "Austin Group is welcome to take a hike". BTW, contrary to the lovely bit of misrepresentation in that thread of theirs (" suggests that" != "someone's comment under LWN article says it _appears_ that"), none of *BSD do it. IMO it's a bad idea. NAKed-by: Al Viro