Linux USB
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Sergey Shtylyov' <s.shtylyov@omp.ru>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: RE: [PATCH] usb: host: ehci-q: make qtd_fill() return 'u16'
Date: Wed, 16 Feb 2022 22:33:15 +0000	[thread overview]
Message-ID: <db41f36420cc4d8585665bf586c1e26e@AcuMS.aculab.com> (raw)
In-Reply-To: <7f2e3194-c897-7ffd-756e-8a9c93d652cd@omp.ru>

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

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

  reply	other threads:[~2022-02-16 22:33 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 [this message]
2022-02-17  1:52   ` Alan Stern
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=db41f36420cc4d8585665bf586c1e26e@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=s.shtylyov@omp.ru \
    --cc=stern@rowland.harvard.edu \
    /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