[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5e03840b-c090-9f30-ae19-ef4d3c2050d8@gmail.com>
Date: Wed, 30 Sep 2020 21:50:57 +0530
From: Anant Thazhemadam <anant.thazhemadam@...il.com>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: Greg KH <greg@...ah.com>, Andrey Konovalov <andreyknvl@...gle.com>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
LKML <linux-kernel@...r.kernel.org>,
Alexander Potapenko <glider@...gle.com>,
syzbot <syzbot+35c80b2190255a410f66@...kaller.appspotmail.com>,
linux-kernel-mentees@...ts.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] KMSAN: uninit-value in rt2500usb_probe_hw
On 30/09/20 9:46 pm, Dmitry Vyukov wrote:
> On Wed, Sep 30, 2020 at 5:57 PM Anant Thazhemadam
> <anant.thazhemadam@...il.com> wrote:
>> 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+35c80b2190255a410f66@...kaller.appspotmail.com> wrote:
>>>>> Hello,
>>>>>
>>>>> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>>>>>
>>>>> Reported-and-tested-by: syzbot+35c80b2190255a410f66@...kaller.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-+Hoj1SUg@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. :)
> I think Greg meant the fix for the general USB brokenness, not a fix
> for this syzbot bug. This bug is not fixed to the best of syzbot
> knowledge.
Ah, okay. My bad. I was wondering why the bug wasn't closed already
if there was already a fix. Thank you for clearing that up :)
Thanks,
Anant
Powered by blists - more mailing lists