All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <mani@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] cpufreq: qcom-cpufreq-hw: fix double IO unmap and resource release on exit
Date: Fri, 24 Mar 2023 15:34:07 +0530	[thread overview]
Message-ID: <20230324100407.GA4259@thinkpad> (raw)
In-Reply-To: <20230323174026.950622-1-krzysztof.kozlowski@linaro.org>

On Thu, Mar 23, 2023 at 06:40:26PM +0100, Krzysztof Kozlowski wrote:
> Commit 054a3ef683a1 ("cpufreq: qcom-hw: Allocate qcom_cpufreq_data
> during probe") moved getting memory resource and iomap from
> qcom_cpufreq_hw_cpu_init() to the probe function, however it left
> untouched cleanup in qcom_cpufreq_hw_cpu_exit().
> 
> During device unbind this will lead to doule release of resource and
> double iounmap(), first by qcom_cpufreq_hw_cpu_exit() and second via
> managed resources:
> 
>   resource: Trying to free nonexistent resource <0x0000000018593000-0x0000000018593fff>
>   Trying to vunmap() nonexistent vm area (0000000088a7d4dc)
>   ...
>   vunmap (mm/vmalloc.c:2771 (discriminator 1))
>   iounmap (mm/ioremap.c:60)
>   devm_ioremap_release (lib/devres.c:19)
>   devres_release_all (drivers/base/devres.c:506 drivers/base/devres.c:535)
>   device_unbind_cleanup (drivers/base/dd.c:523)
>   device_release_driver_internal (drivers/base/dd.c:1248 drivers/base/dd.c:1263)
>   device_driver_detach (drivers/base/dd.c:1300)
>   unbind_store (drivers/base/bus.c:243)
>   drv_attr_store (drivers/base/bus.c:127)
>   sysfs_kf_write (fs/sysfs/file.c:137)
>   kernfs_fop_write_iter (fs/kernfs/file.c:334)
>   vfs_write (include/linux/fs.h:1851 fs/read_write.c:491 fs/read_write.c:584)
>   ksys_write (fs/read_write.c:637)
>   __arm64_sys_write (fs/read_write.c:646)
>   invoke_syscall (arch/arm64/include/asm/current.h:19 arch/arm64/kernel/syscall.c:57)
>   el0_svc_common.constprop.0 (arch/arm64/include/asm/daifflags.h:28 arch/arm64/kernel/syscall.c:150)
>   do_el0_svc (arch/arm64/kernel/syscall.c:194)
>   el0_svc (arch/arm64/include/asm/daifflags.h:28 arch/arm64/kernel/entry-common.c:133 arch/arm64/kernel/entry-common.c:142 arch/arm64/kernel/entry-common.c:638)
>   el0t_64_sync_handler (arch/arm64/kernel/entry-common.c:656)
>   el0t_64_sync (arch/arm64/kernel/entry.S:591)
> 
> Fixes: 054a3ef683a1 ("cpufreq: qcom-hw: Allocate qcom_cpufreq_data during probe")
> Cc: <stable@vger.kernel.org>
> Cc: Manivannan Sadhasivam <mani@kernel.org>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Reviewed-by: Manivannan Sadhasivam <mani@kernel.org>

Thanks,
Mani

> ---
>  drivers/cpufreq/qcom-cpufreq-hw.c | 11 ++---------
>  1 file changed, 2 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/cpufreq/qcom-cpufreq-hw.c b/drivers/cpufreq/qcom-cpufreq-hw.c
> index 2f581d2d617d..b2d2907200a9 100644
> --- a/drivers/cpufreq/qcom-cpufreq-hw.c
> +++ b/drivers/cpufreq/qcom-cpufreq-hw.c
> @@ -43,7 +43,6 @@ struct qcom_cpufreq_soc_data {
>  
>  struct qcom_cpufreq_data {
>  	void __iomem *base;
> -	struct resource *res;
>  
>  	/*
>  	 * Mutex to synchronize between de-init sequence and re-starting LMh
> @@ -590,16 +589,12 @@ static int qcom_cpufreq_hw_cpu_exit(struct cpufreq_policy *policy)
>  {
>  	struct device *cpu_dev = get_cpu_device(policy->cpu);
>  	struct qcom_cpufreq_data *data = policy->driver_data;
> -	struct resource *res = data->res;
> -	void __iomem *base = data->base;
>  
>  	dev_pm_opp_remove_all_dynamic(cpu_dev);
>  	dev_pm_opp_of_cpumask_remove_table(policy->related_cpus);
>  	qcom_cpufreq_hw_lmh_exit(data);
>  	kfree(policy->freq_table);
>  	kfree(data);
> -	iounmap(base);
> -	release_mem_region(res->start, resource_size(res));
>  
>  	return 0;
>  }
> @@ -718,17 +713,15 @@ static int qcom_cpufreq_hw_driver_probe(struct platform_device *pdev)
>  	for (i = 0; i < num_domains; i++) {
>  		struct qcom_cpufreq_data *data = &qcom_cpufreq.data[i];
>  		struct clk_init_data clk_init = {};
> -		struct resource *res;
>  		void __iomem *base;
>  
> -		base = devm_platform_get_and_ioremap_resource(pdev, i, &res);
> +		base = devm_platform_ioremap_resource(pdev, i);
>  		if (IS_ERR(base)) {
> -			dev_err(dev, "Failed to map resource %pR\n", res);
> +			dev_err(dev, "Failed to map resource index %d\n", i);
>  			return PTR_ERR(base);
>  		}
>  
>  		data->base = base;
> -		data->res = res;
>  
>  		/* Register CPU clock for each frequency domain */
>  		clk_init.name = kasprintf(GFP_KERNEL, "qcom_cpufreq%d", i);
> -- 
> 2.34.1
> 

-- 
மணிவண்ணன் சதாசிவம்

  reply	other threads:[~2023-03-24 10:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 17:40 [PATCH] cpufreq: qcom-cpufreq-hw: fix double IO unmap and resource release on exit Krzysztof Kozlowski
2023-03-24 10:04 ` Manivannan Sadhasivam [this message]
2023-03-24 13:37 ` Bjorn Andersson
2023-03-30  3:51 ` Viresh Kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230324100407.GA4259@thinkpad \
    --to=mani@kernel.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=viresh.kumar@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.