[Linux-kernel-mentees] INFO: trying to register non-static key in ath9k_htc_rxep
brookebasile at gmail.com
Wed Sep 23 17:42:55 UTC 2020
On 9/22/20 3:38 AM, Dmitry Vyukov wrote:
> On Tue, Sep 22, 2020 at 9:26 AM Greg Kroah-Hartman
> <gregkh at linuxfoundation.org> wrote:
>> On Tue, Sep 22, 2020 at 08:49:39AM +0200, Dmitry Vyukov wrote:
>>> On Tue, Sep 22, 2020 at 8:21 AM syzbot
>>> <syzbot+4d2d56175b934b9a7bf9 at syzkaller.appspotmail.com> wrote:
>>>> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>>>> Reported-and-tested-by: syzbot+4d2d56175b934b9a7bf9 at syzkaller.appspotmail.com
>>>> Tested on:
>>>> commit: 98477740 Merge branch 'rcu/urgent' of git://git.kernel.org..
>>>> git tree: upstream
>>>> kernel config: https://syzkaller.appspot.com/x/.config?x=2c523334171d074
>>>> dashboard link: https://syzkaller.appspot.com/bug?extid=4d2d56175b934b9a7bf9
>>>> compiler: gcc (GCC) 10.1.0-syz 20200507
>>>> Note: testing is done by a robot and is best-effort only.
>>> Hi Brooke,
>>> As far as I understand, UBS is currently completely broken on upstream
>>> HEAD, so testing any USB bugs on upstream HEAD will lead to false
>>> positive results only.
>> Broken in what way? I don't see any bug reports here...
> I mean this "USB driver ID matching broke":
> syzkaller can't test usb, nor reproduce any existing bugs on the upstream tree.
Thanks for the heads up and for the link to the thread with the information.
I recently fixed the following bug:
I tested this on my local syzkaller instance before sending it in to
syzbot and the kernel panic was resolved, however I did get "-busid- is
not in match_busid table... skip!" in dmesg-- should this be taken as a
false positive as well?
More information about the Linux-kernel-mentees