linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+fdce8f2a8903f3ba0e6b@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_forward_skb
Date: Tue, 12 Mar 2019 01:57:00 -0700	[thread overview]
Message-ID: <0000000000004cfa120583e1dfc3@google.com> (raw)
In-Reply-To: <0000000000009f94c1057e772431@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=16e68713200000
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=15e68713200000
console output: https://syzkaller.appspot.com/x/log.txt?x=11e68713200000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5e7dc790609552d7
dashboard link: https://syzkaller.appspot.com/bug?extid=fdce8f2a8903f3ba0e6b
userspace arch: amd64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15f6d1fd400000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17290fdd400000

Reported-by: syzbot+fdce8f2a8903f3ba0e6b@syzkaller.appspotmail.com
Fixes: ab42f35d ("blk-mq: merge bio into sw queue before plugging")

       reply	other threads:[~2019-03-12  8:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0000000000009f94c1057e772431@google.com>
2019-03-12  8:57 ` syzbot [this message]
2019-03-12 12:01   ` WARNING in hsr_forward_skb Oliver Hartkopp
2019-03-12 16:09     ` Dmitry Vyukov
2019-03-12 16:21       ` Dmitry Vyukov
2019-03-13 18:22         ` Oliver Hartkopp
2021-05-09 15:16 ` [syzbot] " syzbot
2021-05-10  6:09   ` 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=0000000000004cfa120583e1dfc3@google.com \
    --to=syzbot+fdce8f2a8903f3ba0e6b@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).