From: syzbot <syzbot+b92e4f1472a54e1c7dec@syzkaller.appspotmail.com>
To: arvid.brodin@alten.se, axboe@fb.com, axboe@kernel.dk,
davem@davemloft.net, hch@lst.de, linux-block@vger.kernel.org,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
ming.lei@redhat.com, mkl@pengutronix.de, netdev@vger.kernel.org,
socketcan@hartkopp.net, syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in hsr_addr_subst_dest
Date: Mon, 11 Mar 2019 23:27:00 -0700 [thread overview]
Message-ID: <000000000000d7206e0583dfc6b3@google.com> (raw)
In-Reply-To: <0000000000001b1a1d057e776c92@google.com>
syzbot has bisected this bug to:
commit ab42f35d9cb5ac49b5a2a11f940e74f58f207280
Author: Ming Lei <ming.lei@redhat.com>
Date: Fri May 26 11:53:19 2017 +0000
blk-mq: merge bio into sw queue before plugging
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1681996f200000
start commit: ab42f35d blk-mq: merge bio into sw queue before plugging
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=1581996f200000
console output: https://syzkaller.appspot.com/x/log.txt?x=1181996f200000
kernel config: https://syzkaller.appspot.com/x/.config?x=5e7dc790609552d7
dashboard link: https://syzkaller.appspot.com/bug?extid=b92e4f1472a54e1c7dec
userspace arch: amd64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=107db700c00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12304827400000
Reported-by: syzbot+b92e4f1472a54e1c7dec@syzkaller.appspotmail.com
Fixes: ab42f35d ("blk-mq: merge bio into sw queue before plugging")
next prev parent reply other threads:[~2019-03-12 6:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 10:51 WARNING in hsr_addr_subst_dest syzbot
2019-03-12 6:27 ` syzbot [this message]
2019-03-12 12:02 ` Oliver Hartkopp
2019-03-12 16:09 ` Dmitry Vyukov
2020-05-04 3:02 ` syzbot
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=000000000000d7206e0583dfc6b3@google.com \
--to=syzbot+b92e4f1472a54e1c7dec@syzkaller.appspotmail.com \
--cc=arvid.brodin@alten.se \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--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).