All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeffrey Hugo <quic_jhugo@quicinc.com>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: <mhi@lists.linux.dev>, <linux-arm-msm@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bus: mhi: host: Range check CHDBOFF and ERDBOFF
Date: Fri, 24 Mar 2023 07:50:01 -0600	[thread overview]
Message-ID: <11ea2552-27e1-3665-869c-4594de1782a5@quicinc.com> (raw)
In-Reply-To: <20230324103452.GC4259@thinkpad>

On 3/24/2023 4:34 AM, Manivannan Sadhasivam wrote:
> On Fri, Mar 17, 2023 at 09:14:19AM -0600, Jeffrey Hugo wrote:
>> If the value read from the CHDBOFF and ERDBOFF registers is outside the
>> range of the MHI register space then an invalid address might be computed
>> which later causes a kernel panic.  Range check the read value to prevent
>> a crash due to bad data from the device.
>>
>> Fixes: 6cd330ae76ff ("bus: mhi: core: Add support for ringing channel/event ring doorbells")
> 
> Please CC stable list.

The stable folks have been automatically picking up everything with a 
fixes tag for years.  CCing the stable list does not seem to do anything 
unless the patch needs specific backporting adjustments.

Do you still want an explicit CC?

> 
>> Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
>> Reviewed-by: Pranjal Ramajor Asha Kanojiya <quic_pkanojiy@quicinc.com>
>> ---
>>   drivers/bus/mhi/host/init.c | 12 ++++++++++++
>>   1 file changed, 12 insertions(+)
>>
>> diff --git a/drivers/bus/mhi/host/init.c b/drivers/bus/mhi/host/init.c
>> index 3d779ee..ae8ebcfb 100644
>> --- a/drivers/bus/mhi/host/init.c
>> +++ b/drivers/bus/mhi/host/init.c
>> @@ -516,6 +516,12 @@ int mhi_init_mmio(struct mhi_controller *mhi_cntrl)
>>   		return -EIO;
>>   	}
>>   
>> +	if (val >= mhi_cntrl->reg_len - (8 * MHI_DEV_WAKE_DB)) {
>> +		dev_err(dev, "CHDB offset: 0x%x is out of range: 0x%zx\n",
>> +			val, mhi_cntrl->reg_len - (8 * MHI_DEV_WAKE_DB));
>> +		return -EINVAL;
> 
> Isn't -ERANGE a better errno here and also in other places of the driver?

I suppose that could work.  This was modeled after the existing BHI (eg 
BHIOFF) range checks.  You want those updated in the same change or a 
separate one?

> Thanks,
> Mani
> 
>> +	}
>> +
>>   	/* Setup wake db */
>>   	mhi_cntrl->wake_db = base + val + (8 * MHI_DEV_WAKE_DB);
>>   	mhi_cntrl->wake_set = false;
>> @@ -532,6 +538,12 @@ int mhi_init_mmio(struct mhi_controller *mhi_cntrl)
>>   		return -EIO;
>>   	}
>>   
>> +	if (val >= mhi_cntrl->reg_len - (8 * mhi_cntrl->total_ev_rings)) {
>> +		dev_err(dev, "ERDB offset: 0x%x is out of range: 0x%zx\n",
>> +			val, mhi_cntrl->reg_len - (8 * mhi_cntrl->total_ev_rings));
>> +		return -EINVAL;
>> +	}
>> +
>>   	/* Setup event db address for each ev_ring */
>>   	mhi_event = mhi_cntrl->mhi_event;
>>   	for (i = 0; i < mhi_cntrl->total_ev_rings; i++, val += 8, mhi_event++) {
>> -- 
>> 2.7.4
>>
>>
> 


  reply	other threads:[~2023-03-24 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 15:14 [PATCH] bus: mhi: host: Range check CHDBOFF and ERDBOFF Jeffrey Hugo
2023-03-24 10:34 ` Manivannan Sadhasivam
2023-03-24 13:50   ` Jeffrey Hugo [this message]
2023-03-24 14:22     ` 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=11ea2552-27e1-3665-869c-4594de1782a5@quicinc.com \
    --to=quic_jhugo@quicinc.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=mhi@lists.linux.dev \
    /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.