From: Wolfram Sang <wsa@kernel.org>
To: trix@redhat.com
Cc: syniurge@gmail.com, nehal-bakulchandra.shah@amd.com,
shyam-sundar.s-k@amd.com, natechancellor@gmail.com,
ndesaulniers@google.com, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com
Subject: Re: [PATCH] i2c: amd_mp2: handle num is 0 input for i2c_amd_xfer
Date: Mon, 7 Sep 2020 16:28:41 +0200 [thread overview]
Message-ID: <20200907142841.GA3931@ninjato> (raw)
In-Reply-To: <20200904180647.21080-1-trix@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1567 bytes --]
On Fri, Sep 04, 2020 at 11:06:47AM -0700, trix@redhat.com wrote:
> From: Tom Rix <trix@redhat.com>
>
> clang static analyzer reports this problem
>
> i2c-amd-mp2-plat.c:174:9: warning: Branch condition evaluates
> to a garbage value
> return err ? err : num;
> ^~~
>
> err is not initialized, it depends on the being set in the
> transfer loop which will not happen if num is 0. Surveying
> other master_xfer() implementations show all handle a 0 num.
>
> Because returning 0 is expected, initialize err to 0.
Well, it is not expected. The core does:
2019 if (WARN_ON(!msgs || num < 1))
2020 return -EINVAL;
Dunno if we should apply the patch nonetheless or add a comment that num
is guaranteed to be at least 1.
>
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
> drivers/i2c/busses/i2c-amd-mp2-plat.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/i2c/busses/i2c-amd-mp2-plat.c b/drivers/i2c/busses/i2c-amd-mp2-plat.c
> index 17df9e8845b6..506433bc0ff2 100644
> --- a/drivers/i2c/busses/i2c-amd-mp2-plat.c
> +++ b/drivers/i2c/busses/i2c-amd-mp2-plat.c
> @@ -155,7 +155,7 @@ static int i2c_amd_xfer(struct i2c_adapter *adap, struct i2c_msg *msgs, int num)
> struct amd_i2c_dev *i2c_dev = i2c_get_adapdata(adap);
> int i;
> struct i2c_msg *pmsg;
> - int err;
> + int err = 0;
>
> /* the adapter might have been deleted while waiting for the bus lock */
> if (unlikely(!i2c_dev->common.mp2_dev))
> --
> 2.18.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-07 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 18:06 [PATCH] i2c: amd_mp2: handle num is 0 input for i2c_amd_xfer trix
2020-09-05 12:33 ` Elie Morisse
2020-09-07 14:28 ` Wolfram Sang [this message]
2020-09-21 9:39 ` Wolfram Sang
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=20200907142841.GA3931@ninjato \
--to=wsa@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=nehal-bakulchandra.shah@amd.com \
--cc=shyam-sundar.s-k@amd.com \
--cc=syniurge@gmail.com \
--cc=trix@redhat.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