[xfer] Always nullify interface while sending close() message
authorMichael Brown <mcb30@etherboot.org>
Mon, 6 Jul 2009 15:16:59 +0000 (16:16 +0100)
committerMichael Brown <mcb30@etherboot.org>
Mon, 6 Jul 2009 15:16:59 +0000 (16:16 +0100)
commitb7e93a6a55cadbf14fc0fc8f797d2f576c0c5dda
tree710f9f9df383f01722bf854f6ae0003bb4c204cf
parent546cc62394e12aa04eb16da8a47edd7d93869023
[xfer] Always nullify interface while sending close() message

Objects typically call xfer_close() as part of their response to a
close() message.  If the initiating object has already nullified the
xfer interface then this isn't a problem, but it can lead to
unexpected behaviour when the initiating object is aiming to reuse the
connection and so does not nullify the interface.

Fix by always temporarily nullifying the interface during xfer_close()
(as was already being done by xfer_vreopen() in order to work around
this specific problem).

Reported-by: infernix <infernix@infernix.net>
Tested-by: infernix <infernix@infernix.net>
src/core/open.c
src/core/xfer.c