On 22. 12. 2022. 09:04, Tvrtko Ursulin wrote:
In the meantime definitely thanks a lot for testing this quickly and reporting back!
Don't think much of it - anyone with CONFIG_KMEMLEAK enabled could have caught this bug.
I was surprised that you found the fix in less than an hour without me having to bisect :)