From: syzbot <syzbot+ad1f53726c3bd11180cb@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, gregkh@linuxfoundation.org,
jirislaby@kernel.org, jslaby@suse.com, jslaby@suse.cz,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
nico@fluxnic.net, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Write in vcs_read
Date: Sat, 22 Aug 2020 00:31:10 -0700 [thread overview]
Message-ID: <0000000000005d511305ad725632@google.com> (raw)
In-Reply-To: <000000000000e8f42805ad5d136c@google.com>
syzbot has bisected this issue to:
commit b1c32fcfadf5593ab7a63261cc8a5747c36e627e
Author: Jiri Slaby <jslaby@suse.cz>
Date: Tue Aug 18 08:57:05 2020 +0000
vc_screen: extract vcs_read_buf_header
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13259dee900000
start commit: 494d311a Add linux-next specific files for 20200821
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10a59dee900000
console output: https://syzkaller.appspot.com/x/log.txt?x=17259dee900000
kernel config: https://syzkaller.appspot.com/x/.config?x=a61d44f28687f508
dashboard link: https://syzkaller.appspot.com/bug?extid=ad1f53726c3bd11180cb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16704b7e900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1588a046900000
Reported-by: syzbot+ad1f53726c3bd11180cb@syzkaller.appspotmail.com
Fixes: b1c32fcfadf5 ("vc_screen: extract vcs_read_buf_header")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2020-08-22 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000e8f42805ad5d136c@google.com>
2020-08-22 7:31 ` syzbot [this message]
2020-08-22 7:34 ` Jiri Slaby
2020-08-24 8:03 ` Jiri Slaby
2020-08-24 8:22 ` Greg KH
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=0000000000005d511305ad725632@google.com \
--to=syzbot+ad1f53726c3bd11180cb@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=jslaby@suse.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nico@fluxnic.net \
--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