[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1390881491-18998-1-git-send-email-konrad.wilk@oracle.com>
Date: Mon, 27 Jan 2014 22:58:11 -0500
From: Konrad Rzeszutek Wilk <konrad@...nel.org>
To: linux-kernel@...r.kernel.org, rafael.j.wysocki@...el.com,
cpufreq@...r.kernel.org, linux-pm@...r.kernel.org
Cc: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Lukasz Majewski <l.majewski@...sung.com>,
Myungjoo Ham <myungjoo.ham@...sung.com>,
Viresh Kumar <viresh.kumar@...aro.org>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>
Subject: [PATCH] acpi-cpufreq: De-register cpu notifier and free struct msr on error.
If cpufreq_register_driver() fails we would free the acpi driver
related structures but not free the ones allocated
by acpi_cpufreq_boost_init() function. This meant that as
the driver error-ed out and a CPU online/offline event came
we would crash and burn as one of the CPU notifiers would point
to garbage.
This fixes a regression that commit cfc9c8ed03e4d908f2388af8815f44c87b503aaf
"acpi-cpufreq: Adjust the code to use the common boost attribute"
introduced.
CC: Lukasz Majewski <l.majewski@...sung.com>
CC: Myungjoo Ham <myungjoo.ham@...sung.com>
CC: Viresh Kumar <viresh.kumar@...aro.org>
CC: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
CC: Boris Ostrovsky <boris.ostrovsky@...cle.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
---
drivers/cpufreq/acpi-cpufreq.c | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/cpufreq/acpi-cpufreq.c b/drivers/cpufreq/acpi-cpufreq.c
index 79e5608..3e856d6 100644
--- a/drivers/cpufreq/acpi-cpufreq.c
+++ b/drivers/cpufreq/acpi-cpufreq.c
@@ -969,9 +969,10 @@ static int __init acpi_cpufreq_init(void)
acpi_cpufreq_boost_init();
ret = cpufreq_register_driver(&acpi_cpufreq_driver);
- if (ret)
+ if (ret) {
free_acpi_perf_data();
-
+ acpi_cpufreq_boost_exit();
+ }
return ret;
}
--
1.7.7.6
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists