From: syzbot <syzbot+b92e4f1472a54e1c7dec@syzkaller.appspotmail.com>
To: ap420073@gmail.com, arvid.brodin@alten.se, axboe@fb.com,
axboe@kernel.dk, davem@davemloft.net, dvyukov@google.com,
hch@lst.de, kuba@kernel.org, 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: Sun, 03 May 2020 20:02:04 -0700 [thread overview]
Message-ID: <0000000000007851da05a4c9c169@google.com> (raw)
In-Reply-To: <0000000000001b1a1d057e776c92@google.com>
syzbot suspects this bug was fixed by commit:
commit 4b793acdca0050739b99ace6a8b9e7f717f57c6b
Author: Taehee Yoo <ap420073@gmail.com>
Date: Fri Feb 28 18:01:46 2020 +0000
hsr: use netdev_err() instead of WARN_ONCE()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=130746ffe00000
start commit: ea200dec Merge tag 'armsoc-fixes' of git://git.kernel.org/..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=dcf10bf83926432a
dashboard link: https://syzkaller.appspot.com/bug?extid=b92e4f1472a54e1c7dec
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14b5cafee00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12574271e00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: hsr: use netdev_err() instead of WARN_ONCE()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-05-04 3:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000001b1a1d057e776c92@google.com>
2019-03-12 6:27 ` WARNING in hsr_addr_subst_dest syzbot
2019-03-12 12:02 ` Oliver Hartkopp
2019-03-12 16:09 ` Dmitry Vyukov
2020-05-04 3:02 ` syzbot [this message]
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=0000000000007851da05a4c9c169@google.com \
--to=syzbot+b92e4f1472a54e1c7dec@syzkaller.appspotmail.com \
--cc=ap420073@gmail.com \
--cc=arvid.brodin@alten.se \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=hch@lst.de \
--cc=kuba@kernel.org \
--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).