From: Greg KH <gregkh@linuxfoundation.org>
To: "Everest K.C." <everestkc@everestkc.com.np>
Cc: dpenkler@gmail.com, skhan@linuxfoundation.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] staging: gpib: Remove a dead condition in if statement
Date: Wed, 16 Oct 2024 10:04:21 +0200 [thread overview]
Message-ID: <2024101654-jasmine-ransack-7190@gregkh> (raw)
In-Reply-To: <20241016075319.4092-1-everestkc@everestkc.com.np>
On Wed, Oct 16, 2024 at 01:53:18AM -0600, Everest K.C. wrote:
> The variable `residue` is an unsigned int, also the function
> `fluke_get_dma_residue` returns an unsigned int. The value of
> an unsigned int can only be 0 at minimum.
> The less-than-zero comparison can never be true.
> Fix it by removing the dead condition in the if statement.
>
> This issue was reported by Coverity Scan.
> Report:
> CID 1600782: (#1 of 1): Macro compares unsigned to 0 (NO_EFFECT)
> unsigned_compare: This less-than-zero comparison of an unsigned value
> is never true. residue < 0U.
>
> Signed-off-by: Everest K.C. <everestkc@everestkc.com.np>
> ---
> V1 -> V2: - Fixed typo of comparison in changelog
> - Removed Fixes tag
>
> drivers/staging/gpib/eastwood/fluke_gpib.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/gpib/eastwood/fluke_gpib.c b/drivers/staging/gpib/eastwood/fluke_gpib.c
> index f9f149db222d..51b4f9891a34 100644
> --- a/drivers/staging/gpib/eastwood/fluke_gpib.c
> +++ b/drivers/staging/gpib/eastwood/fluke_gpib.c
> @@ -644,7 +644,7 @@ static int fluke_dma_read(gpib_board_t *board, uint8_t *buffer,
> */
> usleep_range(10, 15);
> residue = fluke_get_dma_residue(e_priv->dma_channel, dma_cookie);
> - if (WARN_ON_ONCE(residue > length || residue < 0))
> + if (WARN_ON_ONCE(residue > length))
No, this is incorrect, now we never notice is the call to
fluke_get_dma_residue() has failed. Please fix that bug instead (hint,
Covertity is giving you a pointer to where something might be wrong, but
this change is NOT how to fix it.)
thanks,
greg k-h
next prev parent reply other threads:[~2024-10-16 8:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 7:53 [PATCH V2] staging: gpib: Remove a dead condition in if statement Everest K.C.
2024-10-16 8:04 ` Greg KH [this message]
2024-10-16 12:54 ` Everest K.C.
2024-10-16 15:00 ` Dan Carpenter
2024-10-17 2:47 ` Everest K.C.
2024-10-17 7:03 ` Dan Carpenter
2024-10-16 15:12 ` Greg KH
2024-10-17 2:50 ` Everest K.C.
2024-10-17 4:42 ` Everest K.C.
2024-10-17 6:01 ` Greg KH
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=2024101654-jasmine-ransack-7190@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dpenkler@gmail.com \
--cc=everestkc@everestkc.com.np \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.