* [PATCH] powercap: intel_rapl: Fix kernel panic during PMU unbind
@ 2026-07-26 4:03 Sumeet Pawnikar
2026-08-15 18:45 ` Sumeet R.P.
0 siblings, 1 reply; 2+ messages in thread
From: Sumeet Pawnikar @ 2026-07-26 4:03 UTC (permalink / raw)
To: rafael, linux-pm; +Cc: linux-kernel, sumeet4linux
rapl_package_add_pmu() fails internally at perf_pmu_register(),
and rapl_pmu_update() leaves the global rapl_pmu.pmu structure
zero-initialized via memset and returns an error. But any
previously probed packages retain has_pmu = true.
When the driver is subsequently unbound or removed,
rapl_package_remove_pmu_locked() sees has_pmu == true and
unconditionally calls perf_pmu_unregister(&rapl_pmu.pmu) on the
zeroed-out structure. This attempts a list_del_rcu() on a NULL
list head, immediately causing a kernel panic.
Fix this by checking if the PMU is actually registered before
attempting to unregister it.
Signed-off-by: Sumeet Pawnikar <sumeet4linux@gmail.com>
---
drivers/powercap/intel_rapl_common.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/powercap/intel_rapl_common.c b/drivers/powercap/intel_rapl_common.c
index 1006d183d508..22100f1ca222 100644
--- a/drivers/powercap/intel_rapl_common.c
+++ b/drivers/powercap/intel_rapl_common.c
@@ -1652,7 +1652,8 @@ void rapl_package_remove_pmu_locked(struct rapl_package *rp)
return;
}
- perf_pmu_unregister(&rapl_pmu.pmu);
+ if (rapl_pmu.registered)
+ perf_pmu_unregister(&rapl_pmu.pmu);
memset(&rapl_pmu, 0, sizeof(struct rapl_pmu));
}
EXPORT_SYMBOL_NS_GPL(rapl_package_remove_pmu_locked, "INTEL_RAPL");
--
2.43.0
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] powercap: intel_rapl: Fix kernel panic during PMU unbind
2026-07-26 4:03 [PATCH] powercap: intel_rapl: Fix kernel panic during PMU unbind Sumeet Pawnikar
@ 2026-08-15 18:45 ` Sumeet R.P.
0 siblings, 0 replies; 2+ messages in thread
From: Sumeet R.P. @ 2026-08-15 18:45 UTC (permalink / raw)
To: rafael, linux-pm; +Cc: linux-kernel
On Sun, Jul 26, 2026 at 9:33 AM Sumeet Pawnikar <sumeet4linux@gmail.com> wrote:
>
> rapl_package_add_pmu() fails internally at perf_pmu_register(),
> and rapl_pmu_update() leaves the global rapl_pmu.pmu structure
> zero-initialized via memset and returns an error. But any
> previously probed packages retain has_pmu = true.
>
> When the driver is subsequently unbound or removed,
> rapl_package_remove_pmu_locked() sees has_pmu == true and
> unconditionally calls perf_pmu_unregister(&rapl_pmu.pmu) on the
> zeroed-out structure. This attempts a list_del_rcu() on a NULL
> list head, immediately causing a kernel panic.
>
> Fix this by checking if the PMU is actually registered before
> attempting to unregister it.
>
> Signed-off-by: Sumeet Pawnikar <sumeet4linux@gmail.com>
Hi Rafael,
Gentle ping.
Any chance for this to go into next rc ?
Thanks & Regards,
Sumeet Pawnikar.
> ---
> drivers/powercap/intel_rapl_common.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/powercap/intel_rapl_common.c b/drivers/powercap/intel_rapl_common.c
> index 1006d183d508..22100f1ca222 100644
> --- a/drivers/powercap/intel_rapl_common.c
> +++ b/drivers/powercap/intel_rapl_common.c
> @@ -1652,7 +1652,8 @@ void rapl_package_remove_pmu_locked(struct rapl_package *rp)
> return;
> }
>
> - perf_pmu_unregister(&rapl_pmu.pmu);
> + if (rapl_pmu.registered)
> + perf_pmu_unregister(&rapl_pmu.pmu);
> memset(&rapl_pmu, 0, sizeof(struct rapl_pmu));
> }
> EXPORT_SYMBOL_NS_GPL(rapl_package_remove_pmu_locked, "INTEL_RAPL");
> --
> 2.43.0
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-08-15 18:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-07-26 4:03 [PATCH] powercap: intel_rapl: Fix kernel panic during PMU unbind Sumeet Pawnikar
2026-08-15 18:45 ` Sumeet R.P.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®