From: Pavel Skripkin <paskripkin@gmail.com>
To: Johan Hovold <johan@kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Cc: aelior@marvell.com, skalluru@marvell.com,
GR-everest-linux-l2@marvell.com, davem@davemloft.net,
kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: bnx2x: fix variable dereferenced before check
Date: Thu, 18 Nov 2021 12:00:21 +0300 [thread overview]
Message-ID: <018ada52-3e9b-8909-2346-ea2ce1d817fa@gmail.com> (raw)
In-Reply-To: <YZYULWjK34xL6BeW@hovoldconsulting.com>
On 11/18/21 11:51, Johan Hovold wrote:
> [ Adding Dan. ]
>
> On Sun, Nov 14, 2021 at 01:36:36AM +0300, Pavel Skripkin wrote:
>> Smatch says:
>> bnx2x_init_ops.h:640 bnx2x_ilt_client_mem_op()
>> warn: variable dereferenced before check 'ilt' (see line 638)
>>
>> Move ilt_cli variable initialization _after_ ilt validation, because
>> it's unsafe to deref the pointer before validation check.
>
> It seems smatch is confused here. There is no dereference happening
> until after the check, we're just determining the address when
> initialising ilt_cli.
>
> I know this has been applied, and the change itself is fine, but the
> patch description is wrong and the Fixes tag is unwarranted.
>
I agree. I came up with same thing after the patch has been applied. I
thought about a revert, but seems it's not necessary, since there is no
function change.
I should check smatch warnings more carefully next time, can't say why I
didn't notice it before sending :(
thanks
With regards,
Pavel Skripkin
next prev parent reply other threads:[~2021-11-18 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 22:36 Pavel Skripkin
2021-11-13 22:41 ` Pavel Skripkin
2021-11-15 14:12 ` Jakub Kicinski
2021-11-15 13:30 ` patchwork-bot+netdevbpf
2021-11-18 8:51 ` Johan Hovold
2021-11-18 9:00 ` Pavel Skripkin [this message]
2021-11-18 15:09 ` Dan Carpenter
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=018ada52-3e9b-8909-2346-ea2ce1d817fa@gmail.com \
--to=paskripkin@gmail.com \
--cc=GR-everest-linux-l2@marvell.com \
--cc=aelior@marvell.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=johan@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=skalluru@marvell.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
all inboxes | Powered by JetHome®