Re: [PATCH v1] migration: tls: fix memory leak in migration_tls_get_creds

2020-08-27 Thread Dr. David Alan Gilbert
* Zhenyu Ye (yezhen...@huawei.com) wrote: > Currently migration_tls_get_creds() adds the reference of creds > but there was no place to unref it. So the OBJECT(creds) will > never be freed and result in memory leak. > > The leak stack: > Direct leak of 104 byte(s) in 1 object(s) allocated from:

Re: [PATCH v1] migration: tls: fix memory leak in migration_tls_get_creds

2020-07-22 Thread Daniel P . Berrangé
On Wed, Jul 22, 2020 at 11:32:28AM +0800, Zhenyu Ye wrote: > Currently migration_tls_get_creds() adds the reference of creds > but there was no place to unref it. So the OBJECT(creds) will > never be freed and result in memory leak. > > The leak stack: > Direct leak of 104 byte(s) in 1 object(s)

[PATCH v1] migration: tls: fix memory leak in migration_tls_get_creds

2020-07-21 Thread Zhenyu Ye
Currently migration_tls_get_creds() adds the reference of creds but there was no place to unref it. So the OBJECT(creds) will never be freed and result in memory leak. The leak stack: Direct leak of 104 byte(s) in 1 object(s) allocated from: #0 0xa88bd20b in __interceptor_malloc