The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Can Guo <cang@codeaurora.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	kernel-team@android.com, alim.akhtar@samsung.com,
	avri.altman@wdc.com, bvanassche@acm.org,
	martin.petersen@oracle.com, stanley.chu@mediatek.com,
	Jaegeuk Kim <jaegeuk@google.com>
Subject: Re: [PATCH] scsi: ufs: should not override buffer lengh
Date: Mon, 11 Jan 2021 14:02:20 +0800	[thread overview]
Message-ID: <e1b29f7cdd62cefcc9355baaed66641f@codeaurora.org> (raw)
In-Reply-To: <6551e7d6dd7dc4132dc69e77a51f6f21@codeaurora.org>

Sorry, typo corrected.

Hi Jaegeuk,

I think the problem is that func ufshcd_read_desc_param() is not 
expecting
one access unsupported descriptors on RPMB LU.

If we can get the right buf_len from func 
ufshcd_map_desc_id_to_length(),
the issue won't happen. - 
https://lore.kernel.org/patchwork/patch/1323421/.

What do you think if we update ufshcd_map_desc_id_to_length(add one 
param - desc_index)
so that it can tell the correct buf_len in case of RPMB LU?

Thanks,
Can Guo.

> On 2021-01-11 12:44, Jaegeuk Kim wrote:
>> From: Jaegeuk Kim <jaegeuk@google.com>
>> 
>> Kernel stack violation when getting unit_descriptor/wb_buf_alloc_units 
>> from
>> rpmb lun. The reason is the unit descriptor length is different per 
>> LU.
>> 
>> The lengh of Normal LU is 45, while the one of rpmb LU is 35.
>> 
>> int ufshcd_read_desc_param(struct ufs_hba *hba, ...)
>> {
>> 	param_offset=41;
>> 	param_size=4;
>> 	buff_len=45;
>> 	...
>> 	buff_len=35 by rpmb LU;
>> 
>> 	if (is_kmalloc) {
>> 		/* Make sure we don't copy more data than available */
>> 		if (param_offset + param_size > buff_len)
>> 			param_size = buff_len - param_offset;
>> 			--> param_size = 250;
>> 		memcpy(param_read_buf, &desc_buf[param_offset], param_size);
>> 		--> memcpy(param_read_buf, desc_buf+41, 250);
>> 
>> [  141.868974][ T9174] Kernel panic - not syncing: stack-protector:
>> Kernel stack is corrupted in: wb_buf_alloc_units_show+0x11c/0x11c
>> 	}
>> }
>> 
>> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
>> ---
>>  drivers/scsi/ufs/ufshcd.c | 8 ++++++--
>>  1 file changed, 6 insertions(+), 2 deletions(-)
>> 
>> diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
>> index 2a715f13fe1d..722697b57777 100644
>> --- a/drivers/scsi/ufs/ufshcd.c
>> +++ b/drivers/scsi/ufs/ufshcd.c
>> @@ -3293,8 +3293,12 @@ int ufshcd_read_desc_param(struct ufs_hba *hba,
>> 
>>  	if (is_kmalloc) {
>>  		/* Make sure we don't copy more data than available */
>> -		if (param_offset + param_size > buff_len)
>> -			param_size = buff_len - param_offset;
>> +		if (param_offset + param_size > buff_len) {
>> +			if (buff_len > param_offset)
>> +				param_size = buff_len - param_offset;
>> +			else
>> +				param_size = 0;
>> +		}
>>  		memcpy(param_read_buf, &desc_buf[param_offset], param_size);
>>  	}
>>  out:

  reply	other threads:[~2021-01-11  6:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11  4:44 [PATCH] scsi: ufs: should not override buffer lengh Jaegeuk Kim
2021-01-11  5:53 ` Can Guo
2021-01-11  6:02   ` Can Guo [this message]
2021-01-11  8:15     ` Avri Altman
2021-01-11  8:19       ` Can Guo
2021-01-11  8:46         ` Jaegeuk Kim

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=e1b29f7cdd62cefcc9355baaed66641f@codeaurora.org \
    --to=cang@codeaurora.org \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=bvanassche@acm.org \
    --cc=jaegeuk@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=stanley.chu@mediatek.com \
    /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