bridge: Always call smap_destroy() after smap_init()
authorAlex Wang <alexw@nicira.com>
Thu, 12 Sep 2013 18:54:16 +0000 (11:54 -0700)
committerBen Pfaff <blp@nicira.com>
Thu, 12 Sep 2013 18:54:34 +0000 (11:54 -0700)
commit70fa1ecbf4f013566734fc506f50d90ee570a3e0
tree5d1cc250c1a2e9351b84e06df953fc0b68cbed90
parent067f1e2329d3624330560beadb9e805938e9d67b
bridge: Always call smap_destroy() after smap_init()

This commit fixes a place in bridge.c where smap_destroy() is not
always called after smap_init().  Though there is no memory leak
now, it is necessary to fix it and prevent memory leak in the
future when smap_init() may be modified to allocate dynamic memory.

Reported-by: Ansis Atteka <aatteka@nicira.com>
Signed-off-by: Alex Wang <alexw@nicira.com>
Signed-off-by: Ben Pfaff <blp@nicira.com>
vswitchd/bridge.c