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 21:33:41 +0000 (14:33 -0700)
commit0701e67ea05621889a8fa39156571db82186b120
tree605e5ce06a8db0cc5f1a42b0241601b81aacf01d
parent1b18fb013505891b887a4c97826d64576019bca7
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