On 08/17/2016 10:16 AM, Binyamin Sharet wrote:
> Hi,
>
> On 08/17/2016 10:07 AM, Greg KH wrote:
>> On Wed, Aug 17, 2016 at 09:05:34AM +0200, Greg KH wrote:
>>> On Wed, Aug 17, 2016 at 09:26:18AM +0300, Binyamin Sharet wrote:
>>>> Hi,
>>>>
>>>> On 08/16/2016 05:39 PM, Alan Stern wrote:
>>>>> On Tue, 16 Aug 2016, Binyamin Sharet wrote:
>>>>>
>>>>>> Kernel version: raspberrypi 4.4.6-v7+ #871
>>>>>> Driver source file: drivers/input/misc/ati_remote2.c
>>>>>> Umap2 command line: umap2vsscan -P <PHY> -s 0471:0602
>>>>>>
>>>>>> After connecting such a device, NULL pointer dereference in the kernel
>>>>>> and USB stops responding.
>>>>>>
>>>>>> Binyamin Sharet
>>>>>> Cisco, STARE-C
>>>>>>
>>>>>> << Attached: 0471_0602_dmesg.log >>
>>>>> This bug was fixed by commit 950336ba3e4a ("Input: ati_remote2 - fix
>>>>> crashes on detecting device with invalid descriptor") in the 4.6
>>>>> kernel. The commit was marked for inclusion in the stable kernel
>>>>> series, but it might not be included in 4.4.6.
>>>>>
>>>>> Alan Stern
>>>>>
>>>> I have retested this issue with ubuntu 16.04, using kernel 4.7-rc2
>>>> this is the version that I was asked to test with on another issue
>>>> and was not reproduced. In dmseg I got the message: "ati_remote need
>>>> 2 interfaces, found 1".
>>>>
>>>> I am not sure that it mean it was fixed, and I will need to retest it
>>>> with two interfaces, but I am not sure.
>>>>
>>>> Please let me know if I should be testing with a kernel version other
>>>> than 4.7-rc2, as I'm not familiar with the procedures.
>>> 4.7-rc2 is great, thanks for doing this.
>> Oops, sorry, I mean 4.8-rc2 is the latest. Just grab Linus's git tree,
>> that should be the best overall to test with, even when we get the
>> numbers mixed up :)
>>
>> thanks,
>>
>> greg k-h
> Updating my test system now, will retest all 11 cases and get
> back with the results.
>
kernel: 4.8-rc2
result: not reproduced
--
Binyamin Sharet,
Cisco, STARE-C
--
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
