public inbox for linux-arm-msm@vger.kernel.org
 help / color / mirror / Atom feed
From: Bhaumik Bhatt <bbhatt@codeaurora.org>
To: Jeffrey Hugo <jhugo@codeaurora.org>
Cc: Loic Poulain <loic.poulain@linaro.org>,
	manivannan.sadhasivam@linaro.org, hemantk@codeaurora.org,
	linux-arm-msm@vger.kernel.org,
	jhugo=codeaurora.org@codeaurora.org
Subject: Re: [PATCH] mhi: Fix invalid error returning in mhi_queue
Date: Thu, 25 Feb 2021 10:35:13 -0800	[thread overview]
Message-ID: <1bcb75145c431488164f772216007441@codeaurora.org> (raw)
In-Reply-To: <b2ddde03-cc80-ad5a-97b0-62ea2091271b@codeaurora.org>

On 2021-02-25 08:18 AM, Jeffrey Hugo wrote:
> On 2/25/2021 3:13 AM, Loic Poulain wrote:
>> mhi_queue returns an error when the doorbell is not accessible in
>> the current state. This can happen when the device is in non M0
>> state, like M3, and needs to be waken-up prior ringing the DB. this
>> case is manager earlier by triggering an asynchronous M3 exit via
> 
> "This case is managed"?
> 
>> controller resume/suspend callbacks, that in turn will cause M0
>> transition and DB update.
>> 
>> So, since it's not an error but just delaying of doorbell update do 
>> not
>> return an error.
>> 
>> That also fix a use after free error for skb case, indeed a caller
> 
> "This also fixes"?
> 
>> queuing skb will try to free the skb if the queueing fails, but in
>> that case queueing has been done.
>> 
>> Signed-off-by: Loic Poulain <loic.poulain@linaro.org>
> 
> Is Fixes appropriate since you mention fixing a use after free?
> 
>> ---
>>   drivers/bus/mhi/core/main.c | 8 ++------
>>   1 file changed, 2 insertions(+), 6 deletions(-)
>> 
>> diff --git a/drivers/bus/mhi/core/main.c b/drivers/bus/mhi/core/main.c
>> index 7fc2482..c780234 100644
>> --- a/drivers/bus/mhi/core/main.c
>> +++ b/drivers/bus/mhi/core/main.c
>> @@ -1031,12 +1031,8 @@ static int mhi_queue(struct mhi_device 
>> *mhi_dev, struct mhi_buf_info *buf_info,
>>   	if (mhi_chan->dir == DMA_TO_DEVICE)
>>   		atomic_inc(&mhi_cntrl->pending_pkts);
>>   -	if (unlikely(!MHI_DB_ACCESS_VALID(mhi_cntrl))) {
>> -		ret = -EIO;
>> -		goto exit_unlock;
>> -	}
>> -
>> -	mhi_ring_chan_db(mhi_cntrl, mhi_chan);
>> +	if (likely(MHI_DB_ACCESS_VALID(mhi_cntrl)))
>> +		mhi_ring_chan_db(mhi_cntrl, mhi_chan);
>>     exit_unlock:
>>   	read_unlock_irqrestore(&mhi_cntrl->pm_lock, flags);
>> 
> 
> Seems good to me.  Feel free to add the below on the next revision -
> Reviewed-by: Jeffrey Hugo <jhugo@codeaurora.org>

Agree with Jeff. Just as a suggestion, I recommend running the commit 
text
through grammarly or any such service once before posting it to avoid 
back
and forth over it.

Reviewed-by: Bhaumik Bhatt <bbhatt@codeaurora.org>

Thanks,
Bhaumik
---
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora 
Forum,
a Linux Foundation Collaborative Project

      reply	other threads:[~2021-02-25 18:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 10:13 [PATCH] mhi: Fix invalid error returning in mhi_queue Loic Poulain
2021-02-25 16:18 ` Jeffrey Hugo
2021-02-25 18:35   ` Bhaumik Bhatt [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=1bcb75145c431488164f772216007441@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=loic.poulain@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox