Re: [PATCH v2] Implement close-on-fork
From: Matthew Wilcox <willy@infradead.org>
Date: 2020-05-15 15:57:53
Also in:
linux-alpha, linux-arch, linux-fsdevel, lkml, sparclinux
From: Matthew Wilcox <willy@infradead.org>
Date: 2020-05-15 15:57:53
Also in:
linux-alpha, linux-arch, linux-fsdevel, lkml, sparclinux
On Fri, May 15, 2020 at 10:23:17AM -0500, Nate Karstens wrote:
Series of 4 patches to implement close-on-fork. Tests have been published to https://github.com/nkarstens/ltp/tree/close-on-fork and cover close-on-fork functionality in the following syscalls:
[...]
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).
NAK to this patch series, and the entire concept. Is there a way to persuade POSIX that they made a bad decision by standardising this mess?