From: syzbot <syzbot+aed06913f36eff9b544e@syzkaller.appspotmail.com>
To: anton@tuxera.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-ntfs-dev@lists.sourceforge.net, matthias.bgg@gmail.com,
olof@lixom.net, s.hauer@pengutronix.de,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: slab-out-of-bounds Read in ntfs_attr_find
Date: Wed, 27 Nov 2019 22:52:00 -0800 [thread overview]
Message-ID: <000000000000db46890598628cf4@google.com> (raw)
In-Reply-To: <001a11447acae6b4560568e08829@google.com>
syzbot has bisected this bug to:
commit 9dd068a4b85a68733213c874d08ef768bbec8d01
Author: Matthias Brugger <matthias.bgg@gmail.com>
Date: Fri Jul 31 15:03:13 2015 +0000
soc: mediatek: Fix SCPSYS compilation
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10880f02e00000
start commit: 0adb3285 Linux 4.16
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=12880f02e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=14880f02e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=df0c336cc3b55d45
dashboard link: https://syzkaller.appspot.com/bug?extid=aed06913f36eff9b544e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1430ded3800000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1533214b800000
Reported-by: syzbot+aed06913f36eff9b544e@syzkaller.appspotmail.com
Fixes: 9dd068a4b85a ("soc: mediatek: Fix SCPSYS compilation")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
parent reply other threads:[~2019-11-28 6:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <001a11447acae6b4560568e08829@google.com>]
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=000000000000db46890598628cf4@google.com \
--to=syzbot+aed06913f36eff9b544e@syzkaller.appspotmail.com \
--cc=anton@tuxera.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=matthias.bgg@gmail.com \
--cc=olof@lixom.net \
--cc=s.hauer@pengutronix.de \
--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).