From: Viresh Kumar <viresh.kumar@linaro.org>
To: chenqiwu <qiwuchen55@gmail.com>
Cc: kgene@kernel.org, krzk@kernel.org, rjw@rjwysocki.net,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpufreq: s3c: avoid use after free issue in xxx_cpufreq_reboot_notifier_evt()
Date: Tue, 7 Jan 2020 10:59:20 +0530 [thread overview]
Message-ID: <20200107052920.biwi2cdmz46antm7@vireshk-i7> (raw)
In-Reply-To: <20200106083018.GA19697@cqw-OptiPlex-7050>
On 06-01-20, 16:30, chenqiwu wrote:
> Hhh..I don't agree this, since the cpufreq policy of cpu0 may have
> been released before such UAF issue happenning.
That won't happen if you do cpufreq_cpu_get(), isn't it ?
> By the way, why not get invaild cpufreq policy of another cpu but
> only cpu0 here?
Probably because this platform has a single cpufreq policy which covers all the
CPUs and so it doesn't really matter which CPU you use to get the policy.
--
viresh
prev parent reply other threads:[~2020-01-07 5:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-28 6:43 [PATCH] cpufreq: s3c: avoid use after free issue in xxx_cpufreq_reboot_notifier_evt() qiwuchen55
2020-01-06 5:48 ` Viresh Kumar
2020-01-06 6:52 ` chenqiwu
2020-01-06 6:55 ` Viresh Kumar
2020-01-06 8:30 ` chenqiwu
2020-01-07 5:29 ` 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=20200107052920.biwi2cdmz46antm7@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=qiwuchen55@gmail.com \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).