On Tue, Feb 09, 2016 at 02:22:21PM -0500, Stefan Berger wrote: > It doesn't seem right to simply close the file descriptor on the > process if something goes wrong. The process couldn't close() on it > since another thread could have gotten the same fd number for something > else. I haven't seen a file descriptor that one must not close() in > user space.
The kernel should never unilaterally close a fd, just make it permanently error, like a far-end closed socket. Read fails, write fails, and poll returns readable. User space will close it when it detects read failure. Jason ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ tpmdd-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
