From: syzbot <syzbot+0c601d7fbb8122d39093@syzkaller.appspotmail.com>
To: benjamin.tissoires@gmail.com, benjamin.tissoires@redhat.com,
brookebasile@gmail.com, dh.herrmann@googlemail.com,
jikos@kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, maz@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: INFO: trying to register non-static key in uhid_dev_destroy
Date: Mon, 05 Oct 2020 21:54:05 -0700 [thread overview]
Message-ID: <00000000000074076405b0f9632a@google.com> (raw)
In-Reply-To: <00000000000054c0d105a0328487@google.com>
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
next prev parent reply other threads:[~2020-10-06 4:54 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 [this message]
2020-11-11 13:22 ` Dmitry Vyukov
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=00000000000074076405b0f9632a@google.com \
--to=syzbot+0c601d7fbb8122d39093@syzkaller.appspotmail.com \
--cc=benjamin.tissoires@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=brookebasile@gmail.com \
--cc=dh.herrmann@googlemail.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--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.