On Mon, Jun 13, 2022 at 04:54:07PM +0900, Sergey Senozhatsky wrote: > Hello, > > On (22/06/12 20:56), Naresh Kamboju wrote: > > > > I have tested this patch and the reported issue got resolved [1]. > > > > Many thanks for the tests. > > Quite honestly I was hoping that the patch would not help :) Well, ok, > we now know that it's mapping area lock and the lockdep part of its > memory is zero-ed out. The question is - "why?" It really should not > be zeroed out. Ccing Mike and Sebastian who are author/expert of the culprit patch Naresh found zsmalloc crashed on the testing [1] and confirmed that Sergey's patch[2] fixed the problem. However, I don't understand why we need reinit the local_lock on cpu_up handler[3]. Could you guys shed some light? [1] https://lore.kernel.org/all/CA+G9fYtVOfWWpx96fa3zzKzBPKiNu1w3FOD4j++G8MOG3Vs0EA@xxxxxxxxxxxxxx/ [2] https://lore.kernel.org/all/YqBRZcsfrRMZXMCC@xxxxxxxxxx/ [3] https://lore.kernel.org/all/YqEKapKLBgKEXGBg@xxxxxxxxxx/
