[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d36007da-58a3-da8d-dcad-e41b1c5cffa8@gmail.com>
Date: Fri, 7 Jan 2022 13:18:27 +0300
From: Pavel Skripkin <paskripkin@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: davem@...emloft.net, kuba@...nel.org, tanghui20@...wei.com,
andrew@...n.ch, oneukum@...e.com, arnd@...db.de,
linux-usb@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
syzbot+003c0a286b9af5412510@...kaller.appspotmail.com
Subject: Re: [PATCH] net: mcs7830: handle usb read errors properly
Hi Greg,
On 1/7/22 13:06, Greg KH wrote:
>
> We have a usb core function that handles these "short reads are an
> error" issue. Perhaps usbnet_read_cmd() should be converted to use it
> instead?
>
I thought about it. I am not sure, that there are no callers, that
expect various length data. I remember, that I met such problem in atusb
driver, but it uses plain usb API.
I believe, we can provide new usbnet API, that will use
usb_control_msg_{recv,send} and сarefully convert drivers to use it.
When there won't be any callers of the old one we can just rename it.
I might be missing something about usbnet, so, please, correct me if I
am wrong here :)
With regards,
Pavel Skripkin
Powered by blists - more mailing lists