Re: [PATCH] tracing/timerlat: Check tlat_var for NULL in timerlat_fd_release
From: Steven Rostedt <rostedt@goodmis.org>
Date: 2024-09-04 14:20:04
Also in:
lkml
From: Steven Rostedt <rostedt@goodmis.org>
Date: 2024-09-04 14:20:04
Also in:
lkml
On Tue, 3 Sep 2024 14:47:42 +0200 Tomas Glozar [off-list ref] wrote:
I suggest using the workaround suggested in https://lore.kernel.org/linux-trace-kernel/20240823125426.404f2705@gandalf.local.home (local) for the time being. Together with the patch that adds locks around stopping the threads (https://patchwork.kernel.org/project/linux-trace-kernel/patch/20240823102816.5e55753b@gandalf.local.home/), this should prevent the kernel panic at least until we have a solution for the race itself.
When running my tests, the second one would end up deadlocking and triggering lockdep. I found a way to do basically the same thing with a cpumask and no added locking. I'm currently testing it and will be sending out a patch later today (if it passes the tests). -- Steve