[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200714.140323.590389609923321569.davem@davemloft.net>
Date: Tue, 14 Jul 2020 14:03:23 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: dan.carpenter@...cle.com
Cc: george.kennedy@...cle.com, kuba@...nel.org,
dhaval.giani@...cle.com, netdev@...r.kernel.org
Subject: Re: [PATCH 1/1] ax88172a: fix ax88172a_unbind() failures
From: Dan Carpenter <dan.carpenter@...cle.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@...cle.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.
Powered by blists - more mailing lists