Re: [ovs-dev] [PATCH] ovsdb-server: Fix a reference count leak bug

2016-03-07 Thread Liran Schour
> When destroying an ovsdb_jsonrpc_monitor, the jsonrpc monitor still > holds a reference count to the monitors 'changes' indexed with > 'unflushed' transaction id. The bug is that the reference count was > not decremented as it should in the code path. > > The bug caused 'changes' that have

Re: [ovs-dev] [PATCH] ovsdb-server: Fix a reference count leak bug

2016-03-07 Thread Han Zhou
On Mon, Mar 7, 2016 at 3:44 PM, Andy Zhou wrote: > > When destroying an ovsdb_jsonrpc_monitor, the jsonrpc monitor still > holds a reference count to the monitors 'changes' indexed with > 'unflushed' transaction id. The bug is that the reference count was > not decremented as it

[ovs-dev] [PATCH] ovsdb-server: Fix a reference count leak bug

2016-03-07 Thread Andy Zhou
When destroying an ovsdb_jsonrpc_monitor, the jsonrpc monitor still holds a reference count to the monitors 'changes' indexed with 'unflushed' transaction id. The bug is that the reference count was not decremented as it should in the code path. The bug caused 'changes' that have been flushed to