rx: don't leak a connection hash table in unlikely error condition
authorGarrett Wollman <wollman@csail.mit.edu>
Sun, 15 Jul 2012 19:01:29 +0000 (15:01 -0400)
committerDerrick Brashear <shadow@dementix.org>
Mon, 16 Jul 2012 12:47:30 +0000 (05:47 -0700)
commit53c432d1feba6454af4526b4d797b45a6f205eac
treedc0e71d1d99a05c7b201e0330dfb461a2d2f1446
parent3af6beea4b03bd4dd62b23a6a0df149037b456c0
rx: don't leak a connection hash table in unlikely error condition

If getsockname() returns an error (which shouldn't be possible),
rx_InitHost would leak a connection hash table (which probably
doesn't matter because the caller will just exit anyway).  Make
the analyzer happy by freeing the memory anyway.

Change-Id: If8e78ebfb787d2dc1c0b9f95f91b6e7510c9e307
Reviewed-on: http://gerrit.openafs.org/7768
Reviewed-by: Derrick Brashear <shadow@dementix.org>
Tested-by: BuildBot <buildbot@rampaginggeek.com>
src/rx/rx.c