Hello, On Tue, Jun 04, 2024 at 09:58:04PM +0300, Leon Romanovsky wrote: > But at that point, we didn't add newly created WQ to any list which will execute > that asynchronous release. Did I miss something? So, wq itself is not the problem. There are multiple pwq's that get attached to a wq and each pwq is refcnt'd and released asynchronously. Over time, during wq init, how the error paths behave diverged - pwq's still take the async path while wq error path stayed synchronous. The flush is there to match them. A cleaner solution would be either turning everything async or sync. > Anyway, I understand that the lockdep_register_key() corruption comes > from something else. Do you have any idea what can cause it? How can we > help debug this issue? It looks like other guys are already looking at another commit, but focusing on the backtrace which prematurely freed the reported object (rather than the backtrace which stumbled upon it while walking shared data structure) should help finding the actual culprit. Thanks. -- tejun
