mirror of
https://github.com/ipxe/ipxe
synced 2025-12-22 13:00:39 +03:00
[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>
This commit is contained in:
@@ -45,11 +45,14 @@ static struct xfer_metadata dummy_metadata;
|
||||
*/
|
||||
void xfer_close ( struct xfer_interface *xfer, int rc ) {
|
||||
struct xfer_interface *dest = xfer_get_dest ( xfer );
|
||||
struct xfer_interface_operations *op = xfer->op;
|
||||
|
||||
DBGC ( xfer, "XFER %p->%p close\n", xfer, dest );
|
||||
|
||||
xfer_unplug ( xfer );
|
||||
xfer_nullify ( xfer );
|
||||
dest->op->close ( dest, rc );
|
||||
xfer->op = op;
|
||||
xfer_put ( dest );
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user