Re: kmemleak: sched_domain_shared leaked on asymmetric-capacity + SCHED_CACHE

[K Prateek Nayak]

Hello Breno,

On 7/7/2026 7:01 PM, Breno Leitao wrote:
>> I may have found what might be happening. Since the last SD_SHARE_LLC
>> and the first SD_ASYM_CPUCAPACITY_FULL overlap,
>> init_sched_domain_shared() for SD_SHARE_LLC might just be overwriting
>> the assignment from claim_asym_sched_domain_shared() and we are left
>> with a non-zero refcounted shared that evades claim_allocations() but
>> is not used anywhere either.
>>
>> Breno, could you try the below diff:
> 
> Sure, I've tested it and I don't see the kmemleak report anymore, that
> solved the issue I've raised.
> 
> Feel free to include the following if you are planning to send it to the
> list:
> 
> Tested-by: Breno Leitao <leitao@xxxxxxxxxx>

Thanks a ton! I'll send out an official patch shortly for Peter to pick
up once he is back from holidays after some more testing. Thank you
again for the report and testing. Much appreciated _/\_

-- 
Thanks and Regards,
Prateek