On 26/09/20 12:27 pm, Greg KH wrote:
> On Sat, Sep 26, 2020 at 08:53:07AM +0200, Dmitry Vyukov via 
> Linux-kernel-mentees wrote:
>> On Sat, Sep 26, 2020 at 5:25 AM syzbot
>> <syzbot+35c80b2190255a410...@syzkaller.appspotmail.com> wrote:
>>> Hello,
>>>
>>> syzbot has tested the proposed patch and the reproducer did not trigger any 
>>> issue:
>>>
>>> Reported-and-tested-by: 
>>> syzbot+35c80b2190255a410...@syzkaller.appspotmail.com
>>>
>>> Tested on:
>>>
>>> commit:         c5a13b33 kmsan: clang-format core
>>> git tree:       https://github.com/google/kmsan.git master
>>> kernel config:  https://syzkaller.appspot.com/x/.config?x=41fca8ac7f9e770a
>>> dashboard link: https://syzkaller.appspot.com/bug?extid=35c80b2190255a410f66
>>> compiler:       clang version 10.0.0 (https://github.com/llvm/llvm-project/ 
>>> c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
>>>
>>> Note: testing is done by a robot and is best-effort only.
>> Hi Anant,
>>
>> I see you are testing lots of USB bugs. USB subsystem is currently
>> broken, testing of any USB bugs will give false "no crash" results,
>> see:
>> https://lore.kernel.org/linux-kernel-mentees/cact4y+ymbmrh9gccnczp-fya-dkxx9qhkz+rqxi1f-+hoj1...@mail.gmail.com/
> Fixes for this USB problem are in my tree now and should show up in
> linux-next on Monday.
>
> thanks,
>
> greg k-h

Is there any chance you could identify the commit that fixes this bug?
It would help us close the bug for good. :)

Thanks,
Anant

Reply via email to