Really don't crash if a connection closes early
https://bugzilla.redhat.com/show_bug.cgi?id=1047577 When writing commit 173c2914, I missed the fact virNetServerClientClose unlocks the client object before actually clearing client->sock and thus it is possible to hit a window when client->keepalive is NULL while client->sock is not NULL. I was thinking client->sock == NULL was a better check for a closed connection but apparently we have to go with client->keepalive == NULL to actually fix the crash. Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
Showing
-
mentioned in commit 35ed9796
-
mentioned in commit c385db59
-
mentioned in commit 7fad864a
-
mentioned in commit b24979a1
-
mentioned in commit 9b1e0508
-
mentioned in commit 99f8d97a
-
mentioned in commit 5055fe4b
-
mentioned in commit c86813d5
-
mentioned in commit 08672cff
-
mentioned in commit 2842b103
-
mentioned in commit 8342adef
-
mentioned in commit eb365315
-
mentioned in commit a19f700b
想要评论请 注册 或 登录