From: Dmitry Vyukov <dvyukov@google.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: syzbot <syzbot+fdce8f2a8903f3ba0e6b@syzkaller.appspotmail.com>,
arvid.brodin@alten.se, Jens Axboe <axboe@fb.com>,
Jens Axboe <axboe@kernel.dk>, David Miller <davem@davemloft.net>,
Christoph Hellwig <hch@lst.de>,
linux-block@vger.kernel.org, linux-can@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Ming Lei <ming.lei@redhat.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
netdev <netdev@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: WARNING in hsr_forward_skb
Date: Tue, 12 Mar 2019 17:09:38 +0100 [thread overview]
Message-ID: <CACT4Y+ZoDc=_a_W=wVMYj+VLW8WFBDbQJGB17dZTSvYinWhebA@mail.gmail.com> (raw)
In-Reply-To: <7dd5ffca-803d-9d5e-7fa4-f9eed2249d26@hartkopp.net>
On Tue, Mar 12, 2019 at 1:02 PM Oliver Hartkopp <socketcan@hartkopp.net> wrote:
>
> Hi all,
>
> I'm not sure why a Kernel 4.12.0-rc2+ is used here, but I do not get any
> problems on the my latest 5.0.0-06622-g1fc1cd8399ab tree and I strongly
> assume this patch showing up in 4.12-rc6
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=74b7b490886852582d986a33443c2ffa50970169
>
> fixes the problem.
Hi Oliver,
You can see how bisection progressed and got to 4.12.0-rc2+ in the
bisection log.
The commit that it come up with looks unrelated.
I've started collecting such cases at:
https://github.com/google/syzkaller/issues/1051
and added for this case:
=====
Bisected to wrong commit.
Root cause: broken kernel boots, bugs that happen on all tests.
Boot is broken for several releases with "WARNING in hsr_forward_skb",
this switches to a bug that happens during every test "INFO: trying to
register non-static key in can_notifier", which then leads to a
completely random commit.
=====
> On 3/12/19 9:57 AM, syzbot wrote:
> > 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")
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/7dd5ffca-803d-9d5e-7fa4-f9eed2249d26%40hartkopp.net.
> For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2019-03-12 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 10:31 WARNING in hsr_forward_skb syzbot
2019-03-12 8:57 ` syzbot
2019-03-12 12:01 ` Oliver Hartkopp
2019-03-12 16:09 ` Dmitry Vyukov [this message]
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='CACT4Y+ZoDc=_a_W=wVMYj+VLW8WFBDbQJGB17dZTSvYinWhebA@mail.gmail.com' \
--to=dvyukov@google.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=syzbot+fdce8f2a8903f3ba0e6b@syzkaller.appspotmail.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).