From: George Kennedy <george.kennedy@oracle.com>
To: David Miller <davem@davemloft.net>, dan.carpenter@oracle.com
Cc: kuba@kernel.org, dhaval.giani@oracle.com, netdev@vger.kernel.org
Subject: Re: [PATCH 1/1] ax88172a: fix ax88172a_unbind() failures
Date: Tue, 14 Jul 2020 17:34:33 -0400 [thread overview]
Message-ID: <b7423f65-53d5-35d7-a469-509163c85853@oracle.com> (raw)
In-Reply-To: <20200714.140323.590389609923321569.davem@davemloft.net>
On 7/14/2020 5:03 PM, David Miller wrote:
> From: Dan Carpenter <dan.carpenter@oracle.com>
> Date: Tue, 14 Jul 2020 11:00:38 +0300
>
>> On Mon, Jul 13, 2020 at 05:08:59PM -0700, David Miller wrote:
>>> From: George Kennedy <george.kennedy@oracle.com>
>>> Date: Mon, 13 Jul 2020 07:58:57 -0400
>>>
>>>> @@ -237,6 +237,8 @@ static int ax88172a_bind(struct usbnet *dev, struct usb_interface *intf)
>>>>
>>>> free:
>>>> kfree(priv);
>>>> + if (ret >= 0)
>>>> + ret = -EIO;
>>>> return ret;
>>> Success paths reach here, so ">= 0" is not appropriate. Maybe you
>>> meant "> 0"?
>> No, the success path is the "return 0;" one line before the start of the
>> diff. This is always a failure path.
> Is zero ever a possibility, therefore?
>
> You have two cases, one with an explicit -EIO and another which jumps
> here "if (ret)"
>
> So it seems the answer is no.
The "free:" label is the failure path. The "free:" label can be gotten
to with "ret" >= 0, but the failure path must exit with ret < 0 for
proper failure cleanup.
For example, the failing case here has "ret" = 0 (#define ETH_ALEN 6):
172 static int ax88172a_bind(struct usbnet *dev, struct
usb_interface *intf)
173 {
...
186 /* Get the MAC address */
187 ret = asix_read_cmd(dev, AX_CMD_READ_NODE_ID, 0, 0,
ETH_ALEN, buf, 0);
188 if (ret < ETH_ALEN) {
189 netdev_err(dev->net, "Failed to read MAC
address: %d\n", ret);
190 goto free;
191 }
"drivers/net/usb/ax88172a.c"
The caller to ax88172a_bind() is usbnet_probe() and in the case of
failure, it needs the return value to be < 0.
1653 int
1654 usbnet_probe (struct usb_interface *udev, const struct
usb_device_id *prod)
1655 {
...
1736 if (info->bind) {
1737 status = info->bind (dev, udev);
1738 if (status < 0)
1739 goto out1;
"drivers/net/usb/usbnet.c"
George
next prev parent reply other threads:[~2020-07-14 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 11:58 [PATCH 1/1] ax88172a: fix ax88172a_unbind() failures George Kennedy
2020-07-14 0:08 ` David Miller
2020-07-14 8:00 ` Dan Carpenter
2020-07-14 21:03 ` David Miller
2020-07-14 21:34 ` George Kennedy [this message]
2020-07-14 21:37 ` David Miller
2020-07-15 14:01 ` George Kennedy
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=b7423f65-53d5-35d7-a469-509163c85853@oracle.com \
--to=george.kennedy@oracle.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=dhaval.giani@oracle.com \
--cc=kuba@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;
as well as URLs for NNTP newsgroup(s).