From: Florian Fainelli <f.fainelli@gmail.com>
To: chenqiwu <qiwuchen55@gmail.com>, Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@rjwysocki.net, bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org, mmayer@broadcom.com,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v2] cpufreq: brcmstb-avs-cpufreq: avoid potential stuck and UAF risk
Date: Sat, 18 Jan 2020 20:12:43 -0800 [thread overview]
Message-ID: <fff918f6-a2e2-3789-2fed-8962dc441e4c@gmail.com> (raw)
In-Reply-To: <20200119022513.GA21407@cqw-OptiPlex-7050>
On 1/18/2020 6:25 PM, chenqiwu wrote:
> On Mon, Jan 06, 2020 at 01:01:09PM +0530, Viresh Kumar wrote:
>> 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
> Hi,
> Any progress about this patch?
Viresh gave you some feedback to address, so my understanding is that we
should see a v3.
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-01-19 4:13 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
2020-01-19 2:25 ` chenqiwu
2020-01-19 4:12 ` Florian Fainelli [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=fff918f6-a2e2-3789-2fed-8962dc441e4c@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.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 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox