From: syzbot <syzbot+7d027845265d531ba506@syzkaller.appspotmail.com>
To: daniel.vetter@ffwll.ch, dave@mielke.cc, ghalat@redhat.com,
gregkh@linuxfoundation.org, jslaby@suse.com, kilobyte@angband.pl,
linux-kernel@vger.kernel.org, nico@fluxnic.net, nico@linaro.org,
nicolas.pitre@linaro.org, npitre@baylibre.com, sam@ravnborg.org,
syzkaller-bugs@googlegroups.com, textshell@uchuujin.de,
tomli@tomli.me
Subject: Re: KASAN: slab-out-of-bounds Read in vcs_scr_readw
Date: Fri, 03 Jan 2020 01:48:01 -0800 [thread overview]
Message-ID: <000000000000969b9d059b393473@google.com> (raw)
In-Reply-To: <0000000000005f7f920598d25a5f@google.com>
syzbot suspects this bug was fixed by commit:
commit 0c9acb1af77a3cb8707e43f45b72c95266903cee
Author: Nicolas Pitre <nico@fluxnic.net>
Date: Tue Nov 5 09:33:16 2019 +0000
vcs: prevent write access to vcsu devices
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11602fb6e00000
start commit: 76bb8b05 Merge tag 'kbuild-v5.5' of git://git.kernel.org/p..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=dd226651cb0f364b
dashboard link: https://syzkaller.appspot.com/bug?extid=7d027845265d531ba506
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17c0459ce00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11d4477ae00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: vcs: prevent write access to vcsu devices
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-01-03 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 20:15 KASAN: slab-out-of-bounds Read in vcs_scr_readw syzbot
2019-12-03 21:33 ` Nicolas Pitre
2020-01-03 9:48 ` syzbot [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=000000000000969b9d059b393473@google.com \
--to=syzbot+7d027845265d531ba506@syzkaller.appspotmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dave@mielke.cc \
--cc=ghalat@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kilobyte@angband.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=nico@linaro.org \
--cc=nicolas.pitre@linaro.org \
--cc=npitre@baylibre.com \
--cc=sam@ravnborg.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=textshell@uchuujin.de \
--cc=tomli@tomli.me \
/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