From: Bhaumik Bhatt <bbhatt@codeaurora.org>
To: Jeffrey Hugo <jhugo@codeaurora.org>
Cc: manivannan.sadhasivam@linaro.org, hemantk@codeaurora.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
jhugo=codeaurora.org@codeaurora.org
Subject: Re: [PATCH] mhi_bus: core: Check state before processing power_down
Date: Tue, 16 Feb 2021 14:58:04 -0800 [thread overview]
Message-ID: <6ed2bb4fb04ac47b86ff4bacab1d3b15@codeaurora.org> (raw)
In-Reply-To: <1613511496-22271-1-git-send-email-jhugo@codeaurora.org>
On 2021-02-16 01:38 PM, Jeffrey Hugo wrote:
> We cannot process a power_down if the power state is DISABLED. There
> is
> no valid mhi_ctxt in that case, so attepting to process the power_down
> will likely result in a null pointer dereference. If the power state
> is
> DISABLED, there is nothing to do anyways, so just bail early.
>
> Signed-off-by: Jeffrey Hugo <jhugo@codeaurora.org>
> ---
> drivers/bus/mhi/core/pm.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/bus/mhi/core/pm.c b/drivers/bus/mhi/core/pm.c
> index 56ba3ab..dc69074 100644
> --- a/drivers/bus/mhi/core/pm.c
> +++ b/drivers/bus/mhi/core/pm.c
> @@ -1144,6 +1144,7 @@ int mhi_async_power_up(struct mhi_controller
> *mhi_cntrl)
> mhi_deinit_dev_ctxt(mhi_cntrl);
>
> error_dev_ctxt:
> + mhi_cntrl->pm_state = MHI_PM_DISABLE;
> mutex_unlock(&mhi_cntrl->pm_mutex);
>
> return ret;
> @@ -1155,6 +1156,12 @@ void mhi_power_down(struct mhi_controller
> *mhi_cntrl, bool graceful)
> enum mhi_pm_state cur_state, transition_state;
> struct device *dev = &mhi_cntrl->mhi_dev->dev;
>
> + mutex_lock(&mhi_cntrl->pm_mutex);
> + cur_state = mhi_cntrl->pm_state;
> + mutex_unlock(&mhi_cntrl->pm_mutex);
> + if (cur_state == MHI_PM_DISABLE)
Let's unlock the mutex here and not at the top. We acquire it below
anyway.
> + return; /* Already powered down */
> +
> /* If it's not a graceful shutdown, force MHI to linkdown state */
> transition_state = (graceful) ? MHI_PM_SHUTDOWN_PROCESS :
> MHI_PM_LD_ERR_FATAL_DETECT;
Thanks,
Bhaumik
---
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2021-02-16 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 21:38 [PATCH] mhi_bus: core: Check state before processing power_down Jeffrey Hugo
2021-02-16 22:58 ` Bhaumik Bhatt [this message]
2021-02-17 3:30 ` Manivannan Sadhasivam
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=6ed2bb4fb04ac47b86ff4bacab1d3b15@codeaurora.org \
--to=bbhatt@codeaurora.org \
--cc=hemantk@codeaurora.org \
--cc=jhugo=codeaurora.org@codeaurora.org \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@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 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.