From: Viresh Kumar <viresh.kumar@linaro.org>
To: chenqiwu <qiwuchen55@gmail.com>
Cc: mmayer@broadcom.com, bcm-kernel-feedback-list@broadcom.com,
rjw@rjwysocki.net, f.fainelli@gmail.com,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] cpufreq: brcmstb-avs-cpufreq: avoid potential stuck and UAF risk
Date: Mon, 6 Jan 2020 13:01:09 +0530 [thread overview]
Message-ID: <20200106073109.ndm7enzyznquqps5@vireshk-i7> (raw)
In-Reply-To: <20200106070910.GA17897@cqw-OptiPlex-7050>
On 06-01-20, 15:09, chenqiwu wrote:
> There could be a case as the description of this patch besides
> brcm_avs_driver unloads. Since cpufreq_policy_free() will free
> the mm of cpufreq_policy at the last moment.
Ahh, right. Please fix the other "policy" thing I reported and resend
the patch then.
--
viresh
next prev parent reply other threads:[~2020-01-06 7:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 12:50 [PATCH v2] cpufreq: brcmstb-avs-cpufreq: avoid potential stuck and UAF risk qiwuchen55
2020-01-06 5:56 ` Viresh Kumar
2020-01-06 7:09 ` chenqiwu
2020-01-06 7:31 ` Viresh Kumar [this message]
2020-01-19 2:25 ` chenqiwu
2020-01-19 4:12 ` Florian Fainelli
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=20200106073109.ndm7enzyznquqps5@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mmayer@broadcom.com \
--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).