On (13/04/16 12:09), Pavel Březina wrote:
On 04/12/2016 04:07 PM, Jakub Hrozek wrote:
>On Fri, Apr 08, 2016 at 11:52:18AM +0200, Jakub Hrozek wrote:
>> From c69aff1284c72d1e5bcb633c2499e9fb74f16335 Mon Sep 17 00:00:00 2001
>>From: Jakub Hrozek <jhrozek(a)redhat.com>
>>Date: Wed, 6 Apr 2016 18:35:39 +0200
>>Subject: [PATCH 1/3] memberof: Fix a memory leak when removing ghost users
>
>> From 660413914a9f3061d58acb25a261dcaf3dbbeefe Mon Sep 17 00:00:00 2001
>>From: Jakub Hrozek <jhrozek(a)redhat.com>
>>Date: Fri, 8 Apr 2016 11:47:44 +0200
>>Subject: [PATCH 2/3] memberof: Don't allocate on NULL when deleting
memberUids
>
>ping, I would like to push these two to sssd-1-13 before we release
>1.13.4..
Enable null tracking is called in our leak check. I wonder if we can extend
it to check that NULL context is zero in leak_check_teardown and fix the ldb
leaks?
Might be a good idea. But I have a suspicion that it needn't be trivial
change and we will need to fix also other tests.
In worst case, we can just file a ticket and fix later.
Ack to the patches.
master:
* 883fb900f7c6b202cf0b6d8268ffa626ab8a1be9
* 27a0be2bb6f21f66527e0edea4ed2cb4b5cafa53
* c07fb3f111b4dc2780fa4e1408ea04cd36e95a4d
sssd-1-13:
* 27b035ec987c51e9e9d40ac4586cc1d3b5f07d4d
* 6811a95bb64ef62202dbaf96cfe5bb0b68136d18
* 8527fa9e6fddc1597aa841b25e09cb68e6367381
LS