From: Greg KH <gregkh@linuxfoundation.org>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: heikki.krogerus@linux.intel.com, peter.chen@kernel.org,
linux-usb@vger.kernel.org, imx@lists.linux.dev, jun.li@nxp.com
Subject: Re: [PATCH] usb: chipidea: udc: initialize bounced_size to avoid coverity warning
Date: Fri, 17 Jan 2025 12:09:29 +0100 [thread overview]
Message-ID: <2025011707-sample-unifier-9204@gregkh> (raw)
In-Reply-To: <20250114102815.2311956-1-xu.yang_2@nxp.com>
On Tue, Jan 14, 2025 at 06:28:15PM +0800, Xu Yang wrote:
> The synopsys covertiy tool complains "Using uninitialized value
> bounced_size." at some condition.
>
> sg_dma_len(sg) = min(sg_dma_len(sg), bounced_size);
> ^~~~~~~~~~~~
> Although it can't happen, try remove the warning by initializing it.
No, we don't work around broken tools, fix the tool, don't abuse our
code for that, sorry.
greg k-h
next prev parent reply other threads:[~2025-01-17 11:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 10:28 [PATCH] usb: chipidea: udc: initialize bounced_size to avoid coverity warning Xu Yang
2025-01-17 11:09 ` Greg KH [this message]
2025-01-20 8:57 ` Xu Yang
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=2025011707-sample-unifier-9204@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=imx@lists.linux.dev \
--cc=jun.li@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@kernel.org \
--cc=xu.yang_2@nxp.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