| 2017-02-16 06:59:52 |
Kota Tsuyuzaki |
description |
liberasurecode_reconstruct function with liberasurecode_rs_vand (built-in backend) can leak the allocated memory when trying to reconstruct *parity* fragment.
That was found when we checking all memory leak in the test code at https://review.openstack.org/#/c/434513.
And this is affected also pyeclib and the users (OpenStack Swift is an user of the library)
I confirmed the leak can be reproduced at (at least) PyECLib layer [1] so that object-reconstructor of OpenStack Swift can be affected the leak.
Note that this leak caused at the liberasurecode layer so what both pyeclib and Swift users can do is just upgrading your *liberasurecode* after the fix get merged.
1: https://gist.github.com/bloodeagle40234/bf9eada4ecc41d6516c55fa014c0d78c |
liberasurecode_reconstruct function with liberasurecode_rs_vand (built-in backend) can leak the allocated memory when trying to reconstruct a *parity* fragment.
That was found when we checking all memory leak in the test code at https://review.openstack.org/#/c/434513.
And this is affected also pyeclib and the users (OpenStack Swift is an user of the library)
I confirmed the leak can be reproduced at (at least) PyECLib layer [1] so that object-reconstructor of OpenStack Swift can be affected the leak.
Note that this leak caused at the liberasurecode layer so what both pyeclib and Swift users can do is just upgrading your *liberasurecode* after the fix get merged.
1: https://gist.github.com/bloodeagle40234/bf9eada4ecc41d6516c55fa014c0d78c |
|
