From: Alan Stern <stern@rowland.harvard.edu>
To: David Laight <David.Laight@aculab.com>
Cc: 'Sergey Shtylyov' <s.shtylyov@omp.ru>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] usb: host: ehci-q: make qtd_fill() return 'u16'
Date: Wed, 16 Feb 2022 20:52:51 -0500 [thread overview]
Message-ID: <Yg2qc6Xjbp0NwRDJ@rowland.harvard.edu> (raw)
In-Reply-To: <db41f36420cc4d8585665bf586c1e26e@AcuMS.aculab.com>
On Wed, Feb 16, 2022 at 10:33:15PM +0000, David Laight wrote:
> From: Sergey Shtylyov
> > Sent: 16 February 2022 20:19
> >
> > At the end of qtd_fill(), we assign the 'int count' variable to the 'size_t
> > length' field of 'struct ehci_qtd'. In order not to mix the *signed* and
> > *unsigned* values let's make that variable and the function's result 'u16'
> > as qTD's maximum length is a 15-bit quantity anyway...
>
> Except that you really don't want to be doing arithmetic on sub-register
> sized values.
> On everything except x86 the compiler will have to add instructions
> to mask the value to 16 bits (unless its logic can detect that overflow
> can never happen).
>
> There is a similar problem with parameters and return values.
> They need masking one side of the call (or maybe both).
>
> > Found by Linux Verification Center (linuxtesting.org) with the SVACE static
> > analysis tool.
>
> Which clearly doesn't understand the implications of its reports.
>
> David
Agreed. It would be acceptable to change the types to "unsigned int",
but there's no reason to make them "u16".
In general, the only situation where a size should be smaller than the
native register size is when you're defining fields in a structure or
union, or doing memory-mapped I/O (which often involves the same
thing).
Alan Stern
next prev parent reply other threads:[~2022-02-17 1:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 20:19 [PATCH] usb: host: ehci-q: make qtd_fill() return 'u16' Sergey Shtylyov
2022-02-16 22:33 ` David Laight
2022-02-17 1:52 ` Alan Stern [this message]
2022-02-17 9:20 ` Sergey Shtylyov
2022-02-17 9:29 ` David Laight
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=Yg2qc6Xjbp0NwRDJ@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=David.Laight@aculab.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=s.shtylyov@omp.ru \
/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