From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+0c601d7fbb8122d39093@syzkaller.appspotmail.com>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: INFO: trying to register non-static key in uhid_dev_destroy
Date: Wed, 11 Nov 2020 14:22:23 +0100 [thread overview]
Message-ID: <CACT4Y+a4VWAe4ED7v5+czPc39TATu_ARw6erMikKM8AwpFWYsg@mail.gmail.com> (raw)
In-Reply-To: <00000000000074076405b0f9632a@google.com>
On Tue, Oct 6, 2020 at 6:54 AM syzbot
<syzbot+0c601d7fbb8122d39093@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit bce1305c0ece3dc549663605e567655dd701752c
> Author: Marc Zyngier <maz@kernel.org>
> Date: Sat Aug 29 11:26:01 2020 +0000
>
> HID: core: Correctly handle ReportSize being zero
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10b82f50500000
> start commit: 152036d1 Merge tag 'nfsd-5.7-rc-2' of git://git.linux-nfs...
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=efdde85c3af536b5
> dashboard link: https://syzkaller.appspot.com/bug?extid=0c601d7fbb8122d39093
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10ebad0c100000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d6c21c100000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: HID: core: Correctly handle ReportSize being zero
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
#syz fix: HID: core: Correctly handle ReportSize being zero
prev parent reply other threads:[~2020-11-11 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 16:55 INFO: trying to register non-static key in uhid_dev_destroy syzbot
2020-10-06 4:54 ` syzbot
2020-11-11 13:22 ` Dmitry Vyukov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACT4Y+a4VWAe4ED7v5+czPc39TATu_ARw6erMikKM8AwpFWYsg@mail.gmail.com \
--to=dvyukov@google.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+0c601d7fbb8122d39093@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).