[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <be77e0dd-80c5-ac12-8be5-b2c2b74857f7@suse.com>
Date: Thu, 31 Mar 2022 11:35:35 +0200
From: Oliver Neukum <oneukum@...e.com>
To: Lukas Wunner <lukas@...ner.de>, Oliver Neukum <oneukum@...e.com>
CC: Andrew Lunn <andrew@...n.ch>,
Oleksij Rempel <o.rempel@...gutronix.de>,
Oleksij Rempel <linux@...pel-privat.de>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Heiner Kallweit <hkallweit1@...il.com>
Subject: Re: ordering of call to unbind() in usbnet_disconnect
On 21.03.22 11:17, Lukas Wunner wrote:
> On Thu, Mar 17, 2022 at 04:53:34PM +0100, Oliver Neukum wrote:
>
> By the way: 2c9d6c2b871d caused breakage in smsc95xx.c which was
> subsequently fixed by a049a30fc27c. That in turn required another
> fix, 0bf3885324a8. Some of these code changes will have to be
> rolled back or adjusted after reverting 2c9d6c2b871d. It's a giant mess.
> It's possible that more drivers saw fixes due to 2c9d6c2b871d,
> I haven't checked that yet.
Very well, but in order to do so, I guess we need a fix first.
>
> Oliver, why did you want to revert 2c9d6c2b871d, i.e. in which drivers
> have your users reported breakage? Do you have bugzilla links?
I made the patch in response to a security report about a DOS attack
Regards
Oliver
Powered by blists - more mailing lists