[PATCH] Remove too early null assignment to working rfcomm channel in sap server.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



When dropping rfcomm channel to sap server, the component's channel
cleanup process doesn't trigger disallocation of assigned glib resources
since reference to working channel is already marked as null.
---
 sap/server.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/sap/server.c b/sap/server.c
index c55aa6e..8bd8fe1 100644
--- a/sap/server.c
+++ b/sap/server.c
@@ -1122,7 +1122,6 @@ static void sap_io_destroy(void *data)
 				conn->state == SAP_STATE_GRACEFUL_DISCONNECT)
 			sap_disconnect_req(NULL, 1);
 
-		conn->io = NULL;
 		sap_conn_remove(conn);
 	}
 }
-- 
1.7.6

--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux