public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chanwoo Choi <cwchoi00@gmail.com>
To: Christian 'Ansuel' Marangi <ansuelsmth@gmail.com>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Sibi Sankar <sibis@codeaurora.org>,
	Saravana Kannan <skannan@codeaurora.org>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/5] PM / devfreq: Fix kernel panic with cpu based scaling to passive gov
Date: Wed, 15 Jun 2022 08:06:36 +0900	[thread overview]
Message-ID: <95e3a5ff-3f41-d7bf-fac5-2dbd2832f767@gmail.com> (raw)
In-Reply-To: <20220614110701.31240-4-ansuelsmth@gmail.com>

On 22. 6. 14. 20:06, Christian 'Ansuel' Marangi wrote:
> The cpufreq passive register notifier can PROBE_DEFER and the devfreq
> struct is freed and then reallocaed on probe retry.
> The current logic assume that the code can't PROBE_DEFER so the devfreq
> struct in the this variable in devfreq_passive_data is assumed to be
> (if already set) always correct.
> This cause kernel panic as the code try to access the wrong address.
> To correctly handle this, update the this variable in
> devfreq_passive_data to the devfreq reallocated struct.
> 
> Fixes: a03dacb0316f ("PM / devfreq: Add cpu based scaling support to passive governor")
> Signed-off-by: Christian 'Ansuel' Marangi <ansuelsmth@gmail.com>
> ---
>  drivers/devfreq/governor_passive.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/devfreq/governor_passive.c b/drivers/devfreq/governor_passive.c
> index 3c3322adea03..be8aa6830413 100644
> --- a/drivers/devfreq/governor_passive.c
> +++ b/drivers/devfreq/governor_passive.c
> @@ -395,8 +395,7 @@ static int devfreq_passive_event_handler(struct devfreq *devfreq,
>  	if (!p_data)
>  		return -EINVAL;
>  
> -	if (!p_data->this)
> -		p_data->this = devfreq;
> +	p_data->this = devfreq;
>  
>  	switch (event) {
>  	case DEVFREQ_GOV_START:

Applied it to devfreq-fixes. Thanks.

-- 
Best Regards,
Samsung Electronics
Chanwoo Choi

  reply	other threads:[~2022-06-14 23:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 11:06 [PATCH v3 0/5] PM / devfreq: Various Fixes to cpufreq based passive governor Christian 'Ansuel' Marangi
2022-06-14 11:06 ` [PATCH v3 1/5] PM / devfreq: Fix cpufreq passive unregister erroring on PROBE_DEFER Christian 'Ansuel' Marangi
2022-06-14 22:58   ` Chanwoo Choi
2022-06-14 22:07     ` Ansuel Smith
2022-06-14 23:12       ` Chanwoo Choi
2022-06-14 11:06 ` [PATCH v3 2/5] PM / devfreq: Fix kernel warning with cpufreq passive register fail Christian 'Ansuel' Marangi
2022-06-14 11:06 ` [PATCH v3 3/5] PM / devfreq: Fix kernel panic with cpu based scaling to passive gov Christian 'Ansuel' Marangi
2022-06-14 23:06   ` Chanwoo Choi [this message]
2022-06-14 11:07 ` [PATCH v3 4/5] PM / devfreq: Rework freq_table to be local to devfreq struct Christian 'Ansuel' Marangi
2022-06-14 11:07 ` [PATCH v3 5/5] PM / devfreq: Mute warning on governor PROBE_DEFER Christian 'Ansuel' Marangi
2022-06-14 23:10   ` Chanwoo Choi

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=95e3a5ff-3f41-d7bf-fac5-2dbd2832f767@gmail.com \
    --to=cwchoi00@gmail.com \
    --cc=ansuelsmth@gmail.com \
    --cc=cw00.choi@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=sibis@codeaurora.org \
    --cc=skannan@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox