[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230422192820.59e8e423@barney>
Date: Sat, 22 Apr 2023 19:28:20 +0200
From: Michael Büsch <m@...s.ch>
To: Larry Finger <Larry.Finger@...inger.net>
Cc: Nikita Zhandarovich <n.zhandarovich@...tech.ru>,
Kalle Valo <kvalo@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
"John W. Linville" <linville@...driver.com>,
linux-wireless@...r.kernel.org, b43-dev@...ts.infradead.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
lvc-project@...uxtesting.org,
Natalia Petrova <n.petrova@...tech.ru>
Subject: Re: [PATCH v2] b43legacy: Add checking for null for
ssb_get_devtypedata(dev)
On Fri, 21 Apr 2023 17:14:18 -0500
Larry Finger <Larry.Finger@...inger.net> wrote:
> > (err) goto out;
> > wl = ssb_get_devtypedata(dev);
> > - B43legacy_WARN_ON(!wl);
> > + if (!wl) {
> > + B43legacy_WARN_ON(!wl);
> > + err = -ENODEV;
> > + goto out;
> > + }
> > }
> > err = b43legacy_one_core_attach(dev, wl);
> > if (err)
>
> I do not recall seeing v1. One additional nitpick: The latest
> convention would have the subject as "wifi: b43legacy:...". Kalle may
> be able to fix this on merging, but it not, a v3 might be required.
> Otherwise, the patch is good.
>
> Reviewed-by: Larry Finger <Larry.Finger@...inger.net>
No, it's not good. It's wrong. I already replied to it.
wl can never be NULL here and the goto-out path is wrong (if there
was a chance for it to trigger).
Please drop this patch, Kalle.
--
Michael Büsch
https://bues.ch/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists