From: Roger Quadros <rogerq@kernel.org>
To: coverity-bot <keescook@chromium.org>,
Benedikt Niedermayr <benedikt.niedermayr@siemens.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-kernel@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
linux-next@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: Coverity: gpmc_is_valid_waitpin(): Control flow issues
Date: Mon, 7 Nov 2022 10:53:52 +0200 [thread overview]
Message-ID: <7cdf3d14-3f1b-7cd4-e8b9-e94b5359bf82@kernel.org> (raw)
In-Reply-To: <202211041233.4D45359E7@keescook>
Hi Benedikt,
On 04/11/2022 21:33, coverity-bot wrote:
> Hello!
>
> This is an experimental semi-automated report about issues detected by
> Coverity from a scan of next-20221104 as part of the linux-next scan project:
> https://scan.coverity.com/projects/linux-next-weekly-scan
>
> You're getting this email because you were associated with the identified
> lines of code (noted below) that were touched by commits:
>
> Wed Nov 2 10:02:39 2022 -0400
> 89aed3cd5cb9 ("memory: omap-gpmc: wait pin additions")
>
> Coverity reported the following:
>
> *** CID 1527139: Control flow issues (NO_EFFECT)
> drivers/memory/omap-gpmc.c:1048 in gpmc_is_valid_waitpin()
> 1042 spin_unlock(&gpmc_mem_lock);
> 1043 }
> 1044 EXPORT_SYMBOL(gpmc_cs_free);
> 1045
> 1046 static bool gpmc_is_valid_waitpin(u32 waitpin)
We will need to change this waitpin argument to int.
In addition we will also need to change
struct gpmc_waitpin->pin and struct gpmc_setting->wait_pin
to int as in the code we are relying on GPMC_WAITPIN_INVALID logic which is -1.
> 1047 {
> vvv CID 1527139: Control flow issues (NO_EFFECT)
> vvv This greater-than-or-equal-to-zero comparison of an unsigned value is always true. "waitpin >= 0U".
> 1048 return waitpin >= 0 && waitpin < gpmc_nr_waitpins;
> 1049 }
> 1050
> 1051 static int gpmc_alloc_waitpin(struct gpmc_device *gpmc,
> 1052 struct gpmc_settings *p)
> 1053 {
>
> If this is a false positive, please let us know so we can mark it as
> such, or teach the Coverity rules to be smarter. If not, please make
> sure fixes get into linux-next. :) For patches fixing this, please
> include these lines (but double-check the "Fixes" first):
>
> Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
> Addresses-Coverity-ID: 1527139 ("Control flow issues")
> Fixes: 89aed3cd5cb9 ("memory: omap-gpmc: wait pin additions")
>
> Thanks for your attention!
>
cheers,
-roger
next prev parent reply other threads:[~2022-11-07 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 19:33 Coverity: gpmc_is_valid_waitpin(): Control flow issues coverity-bot
2022-11-07 8:53 ` Roger Quadros [this message]
2022-11-07 8:56 ` Roger Quadros
2022-11-08 8:02 ` Niedermayr, BENEDIKT
2022-11-08 8:15 ` Niedermayr, BENEDIKT
2022-11-08 9:40 ` Krzysztof Kozlowski
2022-11-08 9:39 ` Krzysztof Kozlowski
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=7cdf3d14-3f1b-7cd4-e8b9-e94b5359bf82@kernel.org \
--to=rogerq@kernel.org \
--cc=benedikt.niedermayr@siemens.com \
--cc=gustavo@embeddedor.com \
--cc=keescook@chromium.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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