From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Igor Russkikh <irusskikh@marvell.com>,
Igor Russkikh <Igor.Russkikh@aquantia.com>,
"David S. Miller" <davem@davemloft.net>,
Dmitry Bezrukov <Dmitry.Bezrukov@aquantia.com>,
Nikita Danilov <Nikita.Danilov@aquantia.com>,
Andrew Lunn <andrew@lunn.ch>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [EXT] [PATCH net-next] net: aquantia: fix error handling in aq_nic_init
Date: Mon, 28 Oct 2019 07:00:00 -0500 [thread overview]
Message-ID: <16c059aa-04a9-1301-fa72-eb475f3f3c6f@embeddedor.com> (raw)
In-Reply-To: <ad34c73f-19ee-eb83-221b-cd9fac1d44d5@marvell.com>
On 10/28/19 05:53, Igor Russkikh wrote:
>
>> Fix currenty ignored returned error by properly error checking
>> aq_phy_init().
>>
>> Addresses-Coverity-ID: 1487376 ("Unused value")
>> Fixes: dbcd6806af42 ("net: aquantia: add support for Phy access")
>> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
>> ---
>> drivers/net/ethernet/aquantia/atlantic/aq_nic.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/ethernet/aquantia/atlantic/aq_nic.c b/drivers/net/ethernet/aquantia/atlantic/aq_nic.c
>> index 433adc099e44..1914aa0a19d0 100644
>> --- a/drivers/net/ethernet/aquantia/atlantic/aq_nic.c
>> +++ b/drivers/net/ethernet/aquantia/atlantic/aq_nic.c
>> @@ -341,7 +341,8 @@ int aq_nic_init(struct aq_nic_s *self)
>>
>> if (self->aq_nic_cfg.aq_hw_caps->media_type == AQ_HW_MEDIA_TYPE_TP) {
>> self->aq_hw->phy_id = HW_ATL_PHY_ID_MAX;
>> - err = aq_phy_init(self->aq_hw);
>> + if (!aq_phy_init(self->aq_hw))
>> + goto err_exit;
>> }
>>
>> for (i = 0U, aq_vec = self->aq_vec[0];
>>
>
> Hi Gustavo,
>
Hi!
> I'd say the intention here was to ignore the error, as driver may still live if
> something unexpected happened on Phy access path.
>
I see. Please, see my comments below...
> Notice in the above fix you leave `err` as zero but do error path return -
> that'll break the datapath.
>
You're right. I totally missed that.
> I'd prefer to fix this with simple
>
> (void)aq_phy_init(self->aq_hw);
>
Yep. This is much better. Otherwise, both static analyzers and developers
get confused. :p
Something even better is to add both a cast and a comment explaining why
the return value is not being checked in this case (as you do above).
Thanks
--
Gustavo
prev parent reply other threads:[~2019-10-28 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 6:56 Gustavo A. R. Silva
2019-10-28 10:53 ` [EXT] " Igor Russkikh
2019-10-28 12:00 ` Gustavo A. R. Silva [this message]
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=16c059aa-04a9-1301-fa72-eb475f3f3c6f@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=Dmitry.Bezrukov@aquantia.com \
--cc=Igor.Russkikh@aquantia.com \
--cc=Nikita.Danilov@aquantia.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=irusskikh@marvell.com \
--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
all inboxes | Powered by JetHome®