On Fri, Mar 13, 2026 at 11:09:16AM -0400, Sasha Levin wrote: > + * Calling close() on a file descriptor while another thread is using it > + * (e.g., in a blocking read() or write()) has implementation-defined > + * behavior. On Linux, the blocked operation continues on the underlying > + * file and may complete even after close() returns.
I'm guessing this came from the man pages? This is Linux, so we are the "implementation" here :) thanks, greg k-h
