[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bde8fc1229ec41e99ec77f112cc5ee01@realtek.com>
Date: Fri, 14 May 2021 02:58:00 +0000
From: Hayes Wang <hayeswang@...ltek.com>
To: Alan Stern <stern@...land.harvard.edu>
CC: syzbot <syzbot+95afd23673f5dd295c57@...kaller.appspotmail.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"syzkaller-bugs@...glegroups.com" <syzkaller-bugs@...glegroups.com>,
nic_swsd <nic_swsd@...ltek.com>
Subject: RE: [syzbot] WARNING in rtl8152_probe
Alan Stern <stern@...land.harvard.edu>
> Sent: Thursday, May 13, 2021 10:26 PM
[...]
> Syzbot doesn't test real devices. It tests emulations, and the emulated
> devices usually behave very strangely and in very peculiar and
> unexpected ways, so as to trigger bugs in the kernel. That's why the
> USB devices you see in syzbot logs usually have bizarre descriptors.
Do you mean I have to debug for a device which doesn't exist?
I don't understand why I must consider a fake device
which provide unexpected USB descriptor deliberately?
Best Regards,
Hayes
Powered by blists - more mailing lists