On Wed, Sep 21, 2016 at 06:34:03PM +0200, Oliver Neukum wrote: > On Thu, 2016-08-18 at 13:50 +0300, Binyamin Sharet wrote: > > On 08/18/2016 01:31 PM, Oliver Neukum wrote: > > > On Wed, 2016-08-17 at 14:34 +0300, Binyamin Sharet wrote: > > >>> After connecting such a device, NULL pointer dereference in the > > >> kernel. > > >>> You may need to connect another device or two after this one to > > >> trigger > > >>> the oops. > > >>> > > >>> Binyamin Sharet > > >>> Cisco, STARE-C > > >>> > > >>> << Attached: 160a_3184_dmesg_1.log >> > > >>> << Attached: 160a_3184_dmesg_2.log >> > > >> kernel: 4.8-rc2 > > >> result: reproduced > [..] > > > > > Attached. > > > > Hi, > > this fell through the cracks somehow. Does anybody know how > these devices should be to work with the driver? Which device was this? I'm slowly working on a patchset to move this type of checking to the USB core to hopefully prevent this type of thing from have to be added to each USB driver individually. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
