From: syzbot <syzbot+9d8b6fa6ee7636f350c1@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, arnd@arndb.de, dave@stgolabs.net,
dvyukov@google.com, ebiederm@xmission.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux@dominikbrodowski.net,
manfred@colorfullife.com, syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in freeary
Date: Sun, 24 Mar 2019 11:51:01 -0700 [thread overview]
Message-ID: <000000000000bc42080584db9121@google.com> (raw)
In-Reply-To: <0000000000000e2b4e057c80822f@google.com>
syzbot has bisected this bug to:
commit 86f690e8bfd124c38940e7ad58875ef383003348
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date: Thu Mar 29 12:15:13 2018 +0000
Merge tag 'stm-intel_th-for-greg-20180329' of
git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm into char-misc-next
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17d653a3200000
start commit: 74c4a24d Add linux-next specific files for 20181207
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=143653a3200000
console output: https://syzkaller.appspot.com/x/log.txt?x=103653a3200000
kernel config: https://syzkaller.appspot.com/x/.config?x=6e9413388bf37bed
dashboard link: https://syzkaller.appspot.com/bug?extid=9d8b6fa6ee7636f350c1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16e19da3400000
Reported-by: syzbot+9d8b6fa6ee7636f350c1@syzkaller.appspotmail.com
Fixes: 86f690e8bfd1 ("Merge tag 'stm-intel_th-for-greg-20180329' of
git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm into char-misc-next")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-03-24 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 10:51 general protection fault in freeary syzbot
2018-12-08 11:02 ` Dmitry Vyukov
2019-03-24 18:51 ` syzbot [this message]
2019-03-26 8:43 ` 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=000000000000bc42080584db9121@google.com \
--to=syzbot+9d8b6fa6ee7636f350c1@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dave@stgolabs.net \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@dominikbrodowski.net \
--cc=manfred@colorfullife.com \
--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).