On Fri, 2020-05-15 at 16:07 +0000, Karstens, Nate wrote:

Matthew,

What alternative would you suggest?

From an earlier email:

quoted

...nothing else addresses the underlying issue: there is no way to
prevent a fork() from duplicating the resource. The close-on-exec
flag partially-addresses this by allowing the parent process to
mark a file descriptor as exclusive to itself, but there is still
a period of time the failure can occur because the auto-close only
occurs during the exec(). Perhaps this would not be an issue with
a different process/threading model, but that is another discussion
entirely.

Do you disagree there is an issue?

Oh good grief that's a leading question: When I write bad code and it
crashes, most people would agree there is an issue; very few would
agree the kernel should be changed to fix it. Several of us have
already said the problem seems to be with the way your application is
written.  You didn't even answer emails like this speculating about the
cause being the way your application counts resources:

https://lore.kernel.org/linux-fsdevel/1587569663.3485.18.camel@HansenPartnership.com/ (local)

The bottom line is that we think you could rewrite this one application
not to have the problem you're complaining about rather than introduce
a new kernel API to "fix" it.

James