On Wed, Jun 29, 2022 at 10:37:55AM +0200, Greg KH wrote: > The close is timing out as it tries to flush the data to the device > which is no longer responding. So this kind of is expected behavior, > sorry. That makes sense. I'm guessing that changing this behaviour to be asynchronous would break applications that rely on the return code from close() to say EIO if it does that. > > greg k-h Jookia.
