From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+8357fbef0d7bb602de45@syzkaller.appspotmail.com>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: INFO: trying to register non-static key in uhid_char_release
Date: Wed, 11 Nov 2020 14:21:01 +0100 [thread overview]
Message-ID: <CACT4Y+aqGaM8cGJzqDML8XY49BLr+fa0e9zqKv246s5qmPfyzg@mail.gmail.com> (raw)
In-Reply-To: <0000000000006a67f005b117a94a@google.com>
On Wed, Oct 7, 2020 at 7:01 PM syzbot
<syzbot+8357fbef0d7bb602de45@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=12d19370500000
> start commit: 1127b219 Merge tag 'fallthrough-fixes-5.9-rc3' of git://gi..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=891ca5711a9f1650
> dashboard link: https://syzkaller.appspot.com/bug?extid=8357fbef0d7bb602de45
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=102c472e900000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13081056900000
>
> 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:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 3:05 INFO: trying to register non-static key in uhid_char_release syzbot
[not found] ` <20200308040535.1540-1-hdanton@sina.com>
2020-03-08 6:08 ` Eric Biggers
2020-03-09 15:26 ` syzbot
2020-03-10 0:57 ` syzbot
[not found] ` <20200310031757.12780-1-hdanton@sina.com>
2020-03-21 19:17 ` David Rheinsberg
2020-10-07 17:01 ` syzbot
2020-11-11 13:21 ` 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+aqGaM8cGJzqDML8XY49BLr+fa0e9zqKv246s5qmPfyzg@mail.gmail.com \
--to=dvyukov@google.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+8357fbef0d7bb602de45@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.