From: syzbot <syzbot+5a774ffe70862ca9ebc7@syzkaller.appspotmail.com>
To: arnd@arndb.de, axboe@kernel.dk, corbet@lwn.net,
derek.kiernan@xilinx.com, dhowells@redhat.com,
dragan.cvetic@xilinx.com, ebiggers@google.com,
gregkh@linuxfoundation.org, hare@suse.com, jaegeuk@kernel.org,
james.morris@microsoft.com, jannh@google.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
mchehab+samsung@kernel.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu
Subject: Re: KASAN: slab-out-of-bounds Write in watch_queue_ioctl
Date: Tue, 17 Dec 2019 23:06:00 -0800 [thread overview]
Message-ID: <000000000000bfac3c0599f513fe@google.com> (raw)
In-Reply-To: <00000000000024aa520599f4c933@google.com>
syzbot has bisected this bug to:
commit fe78d401ca6b3639385cf7a9a1597b9cd48f64eb
Author: David Howells <dhowells@redhat.com>
Date: Fri Oct 11 07:48:08 2019 +0000
General notification queue with user mmap()'able ring buffer
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1163cafee00000
start commit: fca4fe89 Add linux-next specific files for 20191217
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=1363cafee00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1563cafee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=634b7ce01f79423d
dashboard link: https://syzkaller.appspot.com/bug?extid=5a774ffe70862ca9ebc7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13df92fee00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1003cafee00000
Reported-by: syzbot+5a774ffe70862ca9ebc7@syzkaller.appspotmail.com
Fixes: fe78d401ca6b ("General notification queue with user mmap()'able ring
buffer")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-12-18 7:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 6:45 KASAN: slab-out-of-bounds Write in watch_queue_ioctl syzbot
2019-12-18 7:06 ` 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=000000000000bfac3c0599f513fe@google.com \
--to=syzbot+5a774ffe70862ca9ebc7@syzkaller.appspotmail.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=derek.kiernan@xilinx.com \
--cc=dhowells@redhat.com \
--cc=dragan.cvetic@xilinx.com \
--cc=ebiggers@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.com \
--cc=jaegeuk@kernel.org \
--cc=james.morris@microsoft.com \
--cc=jannh@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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.