From: syzbot <syzbot+fb77e97ebf0612ee6914@syzkaller.appspotmail.com>
To: airlied@linux.ie, akpm@linux-foundation.org, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, dvyukov@google.com,
keescook@chromium.org, linux-kernel@vger.kernel.org,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
sean@poorly.run, sfr@canb.auug.org.au,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: WARNING in drm_mode_createblob_ioctl
Date: Wed, 06 Nov 2019 07:20:00 -0800 [thread overview]
Message-ID: <00000000000012ff570596af15cc@google.com> (raw)
In-Reply-To: <000000000000b2de3a0594d8b4ca@google.com>
syzbot has bisected this bug to:
commit 9e5a64c71b2f70ba530f8156046dd7dfb8a7a0ba
Author: Kees Cook <keescook@chromium.org>
Date: Mon Nov 4 22:57:23 2019 +0000
uaccess: disallow > INT_MAX copy sizes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=125fe6dce00000
start commit: 51309b9d Add linux-next specific files for 20191105
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=115fe6dce00000
console output: https://syzkaller.appspot.com/x/log.txt?x=165fe6dce00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a9b1a641c1f1fc52
dashboard link: https://syzkaller.appspot.com/bug?extid=fb77e97ebf0612ee6914
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1212dc3ae00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=145f604ae00000
Reported-by: syzbot+fb77e97ebf0612ee6914@syzkaller.appspotmail.com
Fixes: 9e5a64c71b2f ("uaccess: disallow > INT_MAX copy sizes")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-11-06 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 6:09 WARNING in drm_mode_createblob_ioctl syzbot
2019-10-14 9:16 ` Daniel Vetter
2019-10-14 9:39 ` syzbot
2019-10-14 10:43 ` Dmitry Vyukov
2019-11-06 12:30 ` syzbot
2019-11-06 15:20 ` syzbot [this message]
2019-11-06 15:23 ` Daniel Vetter
2019-11-06 15:28 ` Daniel Vetter
2019-11-06 15:33 ` Dmitry Vyukov
2019-11-06 15:56 ` Daniel Vetter
2019-11-06 15:36 ` 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=00000000000012ff570596af15cc@google.com \
--to=syzbot+fb77e97ebf0612ee6914@syzkaller.appspotmail.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvyukov@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sean@poorly.run \
--cc=sfr@canb.auug.org.au \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).