From: Alan Stern <stern@rowland.harvard.edu>
To: Julio Faracco <jcfaracco@gmail.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, axboe@kernel.dk, tglx@linutronix.de,
damien.lemoal@wdc.com, dkadashev@gmail.com,
paul.gortmaker@windriver.com, zhouyanjie@wanyeetech.com,
niklas.cassel@wdc.com, penguin-kernel@i-love.sakura.ne.jp,
macro@orcam.me.uk, caihuoqing@baidu.com
Subject: Re: [PATCH] usb: fixing some clang warnings inside usb host drivers
Date: Sat, 18 Dec 2021 13:05:32 -0500 [thread overview]
Message-ID: <Yb4i7LyYIlJi/9fb@rowland.harvard.edu> (raw)
In-Reply-To: <20211218042420.28466-1-jcfaracco@gmail.com>
On Sat, Dec 18, 2021 at 01:24:20AM -0300, Julio Faracco wrote:
> Clang is reporting some issues related variable values not used and
> other issues inside some USB host drivers. This commit removes some
> trashes and adds some strategies to mitigate those warnings.
>
> The most important is the maxpacket not checking for zeros inside both
> functions qtd_fill(). Even if this variable is always higher than zero,
> it should be checked to avoid this kind of verbosity.
>
> Signed-off-by: Julio Faracco <jcfaracco@gmail.com>
> ---
> drivers/usb/host/ehci-dbg.c | 1 -
> drivers/usb/host/ehci-q.c | 2 +-
> drivers/usb/host/ohci-dbg.c | 1 -
> drivers/usb/host/oxu210hp-hcd.c | 2 +-
> 4 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/usb/host/ehci-dbg.c b/drivers/usb/host/ehci-dbg.c
> index 0b7f1edd9eec..70b4ff65295a 100644
> --- a/drivers/usb/host/ehci-dbg.c
> +++ b/drivers/usb/host/ehci-dbg.c
> @@ -903,7 +903,6 @@ static ssize_t fill_registers_buffer(struct debug_buffer *buf)
> temp = scnprintf(next, size, "complete %ld unlink %ld\n",
> ehci->stats.complete, ehci->stats.unlink);
> size -= temp;
> - next += temp;
Like Joe said, this is a standard pattern (an idiom) and I don't think
it should be changed. Besides, the compiler ought to remove the
unnecessary store automatically.
> diff --git a/drivers/usb/host/ehci-q.c b/drivers/usb/host/ehci-q.c
> index 2cbf4f85bff3..98cb44414e78 100644
> --- a/drivers/usb/host/ehci-q.c
> +++ b/drivers/usb/host/ehci-q.c
> @@ -64,7 +64,7 @@ qtd_fill(struct ehci_hcd *ehci, struct ehci_qtd *qtd, dma_addr_t buf,
> }
>
> /* short packets may only terminate transfers */
> - if (count != len)
> + if (count != len && maxpacket > 0)
> count -= (count % maxpacket);
This is different. But again, I do not think the extra check should be
added. If maxpacket is 0, we _want_ the code to fail in a highly
visible manner -- it would mean there is a bug somewhere else in the
kernel.
> diff --git a/drivers/usb/host/ohci-dbg.c b/drivers/usb/host/ohci-dbg.c
> index 4f267dc93882..6fc9c46ffe3c 100644
> --- a/drivers/usb/host/ohci-dbg.c
> +++ b/drivers/usb/host/ohci-dbg.c
> @@ -561,7 +561,6 @@ static ssize_t fill_periodic_buffer(struct debug_buffer *buf)
>
> } else {
> /* we've seen it and what's after */
> - temp = 0;
> ed = NULL;
> }
This one is a good subject for removal. If you separate this out into
its own patch, I will Ack it.
> diff --git a/drivers/usb/host/oxu210hp-hcd.c b/drivers/usb/host/oxu210hp-hcd.c
> index e82ff2a49672..8a20d9d3c377 100644
> --- a/drivers/usb/host/oxu210hp-hcd.c
> +++ b/drivers/usb/host/oxu210hp-hcd.c
> @@ -1232,7 +1232,7 @@ static int qtd_fill(struct ehci_qtd *qtd, dma_addr_t buf, size_t len,
> }
>
> /* short packets may only terminate transfers */
> - if (count != len)
> + if (count != len && maxpacket > 0)
> count -= (count % maxpacket);
This is essentially the same as the change to ehci-q.c.
In short, if the compiler produces warnings that are inappropriate, it's
an indication that the warnings need to be disabled -- not that the
code needs to be changed.
Alan Stern
next prev parent reply other threads:[~2021-12-18 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 4:24 [PATCH] usb: fixing some clang warnings inside usb host drivers Julio Faracco
2021-12-18 9:13 ` Greg KH
2021-12-18 10:49 ` Joe Perches
2021-12-18 18:05 ` Alan Stern [this message]
2021-12-19 1:41 ` Tetsuo Handa
2021-12-19 2:50 ` Alan Stern
2021-12-19 7:59 ` Tetsuo Handa
2021-12-19 15:46 ` Alan Stern
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=Yb4i7LyYIlJi/9fb@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=axboe@kernel.dk \
--cc=caihuoqing@baidu.com \
--cc=damien.lemoal@wdc.com \
--cc=dkadashev@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jcfaracco@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=niklas.cassel@wdc.com \
--cc=paul.gortmaker@windriver.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=tglx@linutronix.de \
--cc=zhouyanjie@wanyeetech.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