Re: [PATCH v2 1/3] read-cache: plug a few leaks

2013-05-31 Thread Felipe Contreras
On Thu, May 30, 2013 at 10:13 AM, René Scharfe rene.scha...@lsrfire.ath.cx wrote: Am 30.05.2013 15:34, schrieb Felipe Contreras: We don't free 'istate-cache' properly. Apparently 'initialized' doesn't really mean initialized, but loaded, or rather 'not-empty', and the cache can be used even

[PATCH v2 1/3] read-cache: plug a few leaks

2013-05-30 Thread Felipe Contreras
We don't free 'istate-cache' properly. Apparently 'initialized' doesn't really mean initialized, but loaded, or rather 'not-empty', and the cache can be used even if it's not 'initialized', so we can't rely on this variable to keep track of the 'istate-cache'. So assume it always has data, and

Re: [PATCH v2 1/3] read-cache: plug a few leaks

2013-05-30 Thread René Scharfe
Am 30.05.2013 15:34, schrieb Felipe Contreras: We don't free 'istate-cache' properly. Apparently 'initialized' doesn't really mean initialized, but loaded, or rather 'not-empty', and the cache can be used even if it's not 'initialized', so we can't rely on this variable to keep track of the

Re: [PATCH v2 1/3] read-cache: plug a few leaks

2013-05-30 Thread Felipe Contreras
On Thu, May 30, 2013 at 10:13 AM, René Scharfe rene.scha...@lsrfire.ath.cx wrote: Am 30.05.2013 15:34, schrieb Felipe Contreras: We don't free 'istate-cache' properly. Apparently 'initialized' doesn't really mean initialized, but loaded, or rather 'not-empty', and the cache can be used even