From: syzbot <syzbot+8357fbef0d7bb602de45@syzkaller.appspotmail.com>
To: benjamin.tissoires@redhat.com, dh.herrmann@googlemail.com,
ebiggers@kernel.org, hdanton@sina.com, jikos@kernel.org,
jkorsnes@cisco.com, jkosina@suse.cz, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: INFO: trying to register non-static key in uhid_char_release
Date: Mon, 09 Mar 2020 17:57:02 -0700 [thread overview]
Message-ID: <00000000000002735905a07599be@google.com> (raw)
In-Reply-To: <000000000000ce8d2305a03b0988@google.com>
syzbot has bisected this bug to:
commit 84a4062632462c4320704fcdf8e99e89e94c0aba
Author: Johan Korsnes <jkorsnes@cisco.com>
Date: Fri Jan 17 12:08:36 2020 +0000
HID: core: increase HID report buffer size to 8KiB
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=113098b1e00000
start commit: 2c523b34 Linux 5.6-rc5
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=133098b1e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=153098b1e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a5295e161cd85b82
dashboard link: https://syzkaller.appspot.com/bug?extid=8357fbef0d7bb602de45
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11b439c3e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16dc6fb5e00000
Reported-by: syzbot+8357fbef0d7bb602de45@syzkaller.appspotmail.com
Fixes: 84a406263246 ("HID: core: increase HID report buffer size to 8KiB")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-03-10 0:57 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 [this message]
[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
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=00000000000002735905a07599be@google.com \
--to=syzbot+8357fbef0d7bb602de45@syzkaller.appspotmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dh.herrmann@googlemail.com \
--cc=ebiggers@kernel.org \
--cc=hdanton@sina.com \
--cc=jikos@kernel.org \
--cc=jkorsnes@cisco.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.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 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).