All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] usb: storage: Fix overwritten in usb_stor_set_max_xfer_blk()
Date: Fri, 29 Sep 2017 07:36:18 +0800	[thread overview]
Message-ID: <CAEUhbmVj4vjs6mhMHR7e79yb9=kKNF7R9gP3mmX7_eF5vM4Ubw@mail.gmail.com> (raw)
In-Reply-To: <3de48db9-ed77-4d9f-8d87-7cf31c5a7881@denx.de>

Hi Marek,

On Thu, Sep 28, 2017 at 11:24 PM, Marek Vasut <marex@denx.de> wrote:
> On 09/28/2017 06:50 AM, Bin Meng wrote:
>> The stored 'blk' value is overwritten to 'size / 512' before it can
>> be used in usb_stor_set_max_xfer_blk(). This is not what we want.
>> In fact, when 'size' exceeds the upper limit (USHRT_MAX * 512), we
>> should simply assign 'size' to the upper limit.
>>
>> Reported-by: Coverity (CID: 167250)
>> Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
>
> Still failing
> https://travis-ci.org/marex/u-boot-usb/builds/280835848
>

This fixes the Coverity issue, not the 'make tests' issue. Please hold
on apply the xHCI patchset and when the fix is ready I will send v2.

>> ---
>>
>>  common/usb_storage.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/common/usb_storage.c b/common/usb_storage.c
>> index a57570b..a91b1c0 100644
>> --- a/common/usb_storage.c
>> +++ b/common/usb_storage.c
>> @@ -964,7 +964,7 @@ static void usb_stor_set_max_xfer_blk(struct usb_device *udev,
>>               blk = 20;
>>       } else {
>>               if (size > USHRT_MAX * 512)
>> -                     blk = USHRT_MAX;
>> +                     size = USHRT_MAX * 512;
>>               blk = size / 512;
>>       }
>>  #endif
>>

Regards,
Bin

  reply	other threads:[~2017-09-28 23:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28  4:50 [U-Boot] [PATCH] usb: storage: Fix overwritten in usb_stor_set_max_xfer_blk() Bin Meng
2017-09-28 15:24 ` Marek Vasut
2017-09-28 23:36   ` Bin Meng [this message]
2017-09-29  2:30     ` Marek Vasut
2017-09-29  9:26       ` Bin Meng
2017-09-29  9:36         ` Marek Vasut
2017-10-01 13:18           ` Bin Meng
2017-10-01 18:41             ` Marek Vasut

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='CAEUhbmVj4vjs6mhMHR7e79yb9=kKNF7R9gP3mmX7_eF5vM4Ubw@mail.gmail.com' \
    --to=bmeng.cn@gmail.com \
    --cc=u-boot@lists.denx.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.