Author pitrou
Recipients christian.heimes, neologix, pitrou
Date 2017-01-22.13:23:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1485091400.86.0.242896795862.issue29343@psf.upfronthosting.co.za>
In-reply-to
Content
Closing a socket whose fd has already been closed before is a bug waiting to happen.  Indeed it feels harmless if you just get a EBADF, but if the given fd gets reused in the meantime for another file or socket, your close() method is going to close a resource which doesn't belong to the socket (and then the fd can be reused for yet another resource without its owner knowing, and confusion/hilarity ensues).
History
Date User Action Args
2017-01-22 13:23:20pitrousetrecipients: + pitrou, christian.heimes, neologix
2017-01-22 13:23:20pitrousetmessageid: <1485091400.86.0.242896795862.issue29343@psf.upfronthosting.co.za>
2017-01-22 13:23:20pitroulinkissue29343 messages
2017-01-22 13:23:20pitroucreate