From: syzbot <syzbot+c58fa3b1231d2ea0c4d3@syzkaller.appspotmail.com>
To: andy.shevchenko@gmail.com, bgolaszewski@baylibre.com,
bp@alien8.de, davem@davemloft.net, douly.fnst@cn.fujitsu.com,
hpa@zytor.com, jon.maloy@ericsson.com, konrad.wilk@oracle.com,
len.brown@intel.com, linus.walleij@linaro.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, netdev@vger.kernel.org, puwen@hygon.cn,
rppt@linux.vnet.ibm.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, tipc-discussion@lists.sourceforge.net,
x86@kernel.org, ying.xue@windriver.com
Subject: Re: general protection fault in __bfs (2)
Date: Mon, 11 Mar 2019 06:27:01 -0700 [thread overview]
Message-ID: <0000000000001d3a060583d187dd@google.com> (raw)
In-Reply-To: <00000000000086d87305801011c4@google.com>
syzbot has bisected this bug to:
commit 2646b90de5c3492db2ead71337fd4c7d7f549ebe
Author: Linus Walleij <linus.walleij@linaro.org>
Date: Fri Oct 26 08:41:22 2018 +0000
gpio: Add global TODO file for GPIO
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12589f8d200000
start commit: 2646b90d gpio: Add global TODO file for GPIO
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=11589f8d200000
console output: https://syzkaller.appspot.com/x/log.txt?x=16589f8d200000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f00801d7b7c4fe6
dashboard link: https://syzkaller.appspot.com/bug?extid=c58fa3b1231d2ea0c4d3
userspace arch: amd64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15bab650c00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17a331df400000
Reported-by: syzbot+c58fa3b1231d2ea0c4d3@syzkaller.appspotmail.com
Fixes: 2646b90d ("gpio: Add global TODO file for GPIO")
next prev parent reply other threads:[~2019-03-11 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 18:23 general protection fault in __bfs (2) syzbot
2019-02-07 3:42 ` syzbot
2019-03-11 13:27 ` syzbot [this message]
2019-03-11 13:49 ` Andy Shevchenko
2019-03-11 13:49 ` Andy Shevchenko
2019-03-28 16:47 ` Linus Walleij
2019-03-28 16:47 ` Linus Walleij
2020-06-18 22:52 ` syzbot
2020-06-19 12:17 ` Petr Machata
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=0000000000001d3a060583d187dd@google.com \
--to=syzbot+c58fa3b1231d2ea0c4d3@syzkaller.appspotmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=douly.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=jon.maloy@ericsson.com \
--cc=konrad.wilk@oracle.com \
--cc=len.brown@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=puwen@hygon.cn \
--cc=rppt@linux.vnet.ibm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=x86@kernel.org \
--cc=ying.xue@windriver.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 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.