From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Andy Gross <agross@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Evan Green <evgreen@chromium.org>,
Stephen Boyd <swboyd@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>,
Maulik Shah <mkshah@codeaurora.org>,
Alexios Zavras <alexios.zavras@intel.com>,
Colin Cross <ccross@android.com>, Kevin Hilman <khilman@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 3/5] kernel/cpu_pm: Fix uninitted local in cpu_pm
Date: Fri, 15 May 2020 11:50:22 -0700 [thread overview]
Message-ID: <20200515185022.GZ2165@builder.lan> (raw)
In-Reply-To: <CAD=FV=WpYm=1gUW2Tu4YMwDvn8r7_4xYQD2_bQFU=Po76xyowA@mail.gmail.com>
On Thu 14 May 19:32 PDT 2020, Doug Anderson wrote:
> Hi,
>
> On Mon, May 4, 2020 at 10:50 AM Douglas Anderson <dianders@chromium.org> wrote:
> >
> > cpu_pm_notify() is basically a wrapper of notifier_call_chain().
> > notifier_call_chain() doesn't initialize *nr_calls to 0 before it
> > starts incrementing it--presumably it's up to the callers to do this.
> >
> > Unfortunately the callers of cpu_pm_notify() don't init *nr_calls.
> > This potentially means you could get too many or two few calls to
> > CPU_PM_ENTER_FAILED or CPU_CLUSTER_PM_ENTER_FAILED depending on the
> > luck of the stack.
> >
> > Let's fix this.
> >
> > Fixes: ab10023e0088 ("cpu_pm: Add cpu power management notifiers")
> > Signed-off-by: Douglas Anderson <dianders@chromium.org>
> > Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Reviewed-by: Stephen Boyd <swboyd@chromium.org>
> > ---
> > This seems to be an ownerless file. I'm hoping this patch can just go
> > through the Qualcomm tree. It would be nice if we could get an Ack
> > from Rafael or Greg KH though.
>
> Greg / Rafael: any thoughts on this patch? Care to give it an Ack so
> it could go through the Qualcomm tree?
>
> Andrew: I think you are the adopter or orphan patches, usually. If
> nobody else will take this patch, will you consider taking it into
> your tree? It should be a super straightforward bugfix. I'm happy to
> re-post it CCing you if need be.
>
Thanks for the patch and the reviews. I've picked all 5 patches through
my tree, with the added stable@ Cc on this one.
Regards,
Bjorn
next prev parent reply other threads:[~2020-05-15 18:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 17:50 [PATCH v6 1/5] soc: qcom: rpmh-rsc: Correctly ignore CPU_CLUSTER_PM notifications Douglas Anderson
2020-05-04 17:50 ` [PATCH v6 2/5] soc: qcom: rpmh-rsc: We aren't notified of our own failure w/ NOTIFY_BAD Douglas Anderson
2020-05-04 17:50 ` [PATCH v6 3/5] kernel/cpu_pm: Fix uninitted local in cpu_pm Douglas Anderson
2020-05-15 2:32 ` Doug Anderson
2020-05-15 7:26 ` Greg Kroah-Hartman
2020-05-15 18:50 ` Bjorn Andersson [this message]
2020-05-15 7:25 ` Greg Kroah-Hartman
2020-05-04 17:50 ` [PATCH v6 4/5] soc: qcom: rpmh-rsc: Simplify locking by eliminating the per-TCS lock Douglas Anderson
2020-05-04 17:50 ` [PATCH v6 5/5] soc: qcom: rpmh-rsc: Remove the pm_lock Douglas Anderson
2020-05-05 6:31 ` [PATCH v6 1/5] soc: qcom: rpmh-rsc: Correctly ignore CPU_CLUSTER_PM notifications Stephen Boyd
2020-05-15 2:29 ` Doug Anderson
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=20200515185022.GZ2165@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexios.zavras@intel.com \
--cc=ccross@android.com \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=mkshah@codeaurora.org \
--cc=rafael.j.wysocki@intel.com \
--cc=santosh.shilimkar@ti.com \
--cc=swboyd@chromium.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.