From: Viresh Kumar <viresh.kumar@linaro.org>
To: Jia-Ju Bai <baijiaju1990@gmail.com>
Cc: vireshk@kernel.org, nm@ti.com, sboyd@codeaurora.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] opp: cpu: Replace GFP_ATOMIC with GFP_KERNEL in dev_pm_opp_init_cpufreq_table
Date: Thu, 8 Feb 2018 20:15:13 +0530 [thread overview]
Message-ID: <20180208144513.GW28462@vireshk-i7> (raw)
In-Reply-To: <1516956529-32264-1-git-send-email-baijiaju1990@gmail.com>
On 26-01-18, 16:48, Jia-Ju Bai wrote:
> After checking all possible call chains to
> dev_pm_opp_init_cpufreq_table() here,
> my tool finds that this function is never called in atomic context,
> namely never in an interrupt handler or holding a spinlock.
> And dev_pm_opp_init_cpufreq_table() calls dev_pm_opp_get_opp_count(),
> which calls mutex_lock that can sleep.
> It indicates that atmtcp_v_send() can call functions which may sleep.
> Thus GFP_ATOMIC is not necessary, and it can be replaced with GFP_KERNEL.
>
> This is found by a static analysis tool named DCNS written by myself.
>
> Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
> ---
> drivers/opp/cpu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/opp/cpu.c b/drivers/opp/cpu.c
> index 2d87bc1..0c09107 100644
> --- a/drivers/opp/cpu.c
> +++ b/drivers/opp/cpu.c
> @@ -55,7 +55,7 @@ int dev_pm_opp_init_cpufreq_table(struct device *dev,
> if (max_opps <= 0)
> return max_opps ? max_opps : -ENODATA;
>
> - freq_table = kcalloc((max_opps + 1), sizeof(*freq_table), GFP_ATOMIC);
> + freq_table = kcalloc((max_opps + 1), sizeof(*freq_table), GFP_KERNEL);
> if (!freq_table)
> return -ENOMEM;
Applied thanks.
--
viresh
prev parent reply other threads:[~2018-02-08 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 8:48 [PATCH] opp: cpu: Replace GFP_ATOMIC with GFP_KERNEL in dev_pm_opp_init_cpufreq_table Jia-Ju Bai
2018-02-08 14:45 ` Viresh Kumar [this message]
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=20180208144513.GW28462@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=baijiaju1990@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=sboyd@codeaurora.org \
--cc=vireshk@kernel.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