From: Dan Carpenter <dan.carpenter@oracle.com>
To: Colin Ian King <colin.king@canonical.com>
Cc: Aviad Krawczyk <aviad.krawczyk@huawei.com>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] net: hinic: fix comparison of a uint16_t type with -1
Date: Thu, 24 Aug 2017 12:29:51 +0300 [thread overview]
Message-ID: <20170824092951.ozllwwklfld44u5u@mwanda> (raw)
In-Reply-To: <d37c85d8-3954-e7b7-e569-f18c2b062966@canonical.com>
On Thu, Aug 24, 2017 at 09:54:03AM +0100, Colin Ian King wrote:
> On 24/08/17 09:48, Aviad Krawczyk wrote:
> > On 8/23/2017 6:39 PM, Colin King wrote:
> >> From: Colin Ian King <colin.king@canonical.com>
> >>
> >> The comparison of hw_ioctxt.rx_buf_sz_idx == -1 is always false because
> >> rx_buf_sz_idx is a uint16_t. Fix this by explicitly casting -1 to uint16_t.
> >>
> >> Detected by CoverityScan, CID#1454559 ("Operands don't affect result")
> >>
> >> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> >> ---
> >> drivers/net/ethernet/huawei/hinic/hinic_hw_dev.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/net/ethernet/huawei/hinic/hinic_hw_dev.c b/drivers/net/ethernet/huawei/hinic/hinic_hw_dev.c
> >> index 09dec6de8dd5..71e26070fb7f 100644
> >> --- a/drivers/net/ethernet/huawei/hinic/hinic_hw_dev.c
> >> +++ b/drivers/net/ethernet/huawei/hinic/hinic_hw_dev.c
> >> @@ -352,7 +352,7 @@ static int set_hw_ioctxt(struct hinic_hwdev *hwdev, unsigned int rq_depth,
> >> }
> >> }
> >>
> >> - if (hw_ioctxt.rx_buf_sz_idx == -1)
> >> + if (hw_ioctxt.rx_buf_sz_idx == (uint16_t)-1)
> >> return -EINVAL;
> >>
> >> hw_ioctxt.sq_depth = ilog2(sq_depth);
> >>
> >
> > Many thanks, Colin.
> > I prefer to avoid casting when possible, what do you think about replacing the condition by:
> >
> > if (rx_buf_sz_table[i].sz != HINIC_RX_BUF_SZ)
> > return -EINVAL;
> >
>
> Does that work as expected when rx_buf_sz_table[i].sz == -1?
No it doesn't. Please, don't ask rhetorical questions. I have a
toddler and I constantly ask him toddler level questions and it drives
me nuts that all the adults in the room will answer me... "Yes, I
already know that's a cow. I was quizing my son. But thank you!"
Meanwhile I can't resist answering questions myself...
The code looks like this:
drivers/net/ethernet/huawei/hinic/hinic_hw_dev.c
345 hw_ioctxt.rq_depth = ilog2(rq_depth);
346
347 for (i = 0; ; i++) {
348 if ((rx_buf_sz_table[i].sz == HINIC_RX_BUF_SZ) ||
349 (rx_buf_sz_table[i].sz == -1)) {
350 hw_ioctxt.rx_buf_sz_idx = rx_buf_sz_table[i].idx;
351 break;
352 }
353 }
354
355 if (hw_ioctxt.rx_buf_sz_idx == -1)
356 return -EINVAL;
357
The loop doesn't make sense. We are looping through rx_buf_sz_table[]
until we hit 2048 or -1. But 2048 comes first so we always get there
and break.
We may as well replace all that code with:
hw_ioctxt.rx_buf_sz_idx = 11;
Something is very wrong.
regards,
dan carpenter
next prev parent reply other threads:[~2017-08-24 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 15:39 [PATCH][next] net: hinic: fix comparison of a uint16_t type with -1 Colin King
2017-08-24 8:48 ` Aviad Krawczyk
2017-08-24 8:54 ` Colin Ian King
2017-08-24 9:29 ` Dan Carpenter [this message]
2017-08-24 9:38 ` Aviad Krawczyk
2017-08-24 21:32 ` David Miller
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=20170824092951.ozllwwklfld44u5u@mwanda \
--to=dan.carpenter@oracle.com \
--cc=aviad.krawczyk@huawei.com \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox