On Wed, Sep 11, 2013 at 5:19 PM, Alex Wang wrote:
> 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 allo
Thanks for the tip.
I'll resend a v2, ;D
On Thu, Sep 12, 2013 at 9:52 AM, Ansis Atteka wrote:
> On Wed, Sep 11, 2013 at 5:19 PM, Alex Wang wrote:
> > 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
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
Signed-off
