From: syzbot <syzbot+fdce8f2a8903f3ba0e6b@syzkaller.appspotmail.com>
To: arvid.brodin@alten.se, axboe@fb.com, axboe@kernel.dk,
davem@davemloft.net, dvyukov@google.com, edumazet@google.com,
hch@lst.de, kuba@kernel.org, kurt@linutronix.de,
linux-block@vger.kernel.org, linux-can@vger.kernel.org,
linux-kernel@vger.kernel.org, m-karicheri2@ti.com,
ming.lei@redhat.com, mkl@pengutronix.de, netdev@vger.kernel.org,
socketcan@hartkopp.net, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in hsr_forward_skb
Date: Sun, 09 May 2021 08:16:07 -0700 [thread overview]
Message-ID: <000000000000e5b92105c1e723d5@google.com> (raw)
In-Reply-To: <0000000000009f94c1057e772431@google.com>
syzbot suspects this issue was fixed by commit:
commit 9d6803921a16f4d768dc41a75375629828f4d91e
Author: Kurt Kanzenbach <kurt@linutronix.de>
Date: Tue Apr 6 07:35:09 2021 +0000
net: hsr: Reset MAC header for Tx path
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=119c7fedd00000
start commit: 3af409ca net: enetc: fix destroyed phylink dereference dur..
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=8cb23303ddb9411f
dashboard link: https://syzkaller.appspot.com/bug?extid=fdce8f2a8903f3ba0e6b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1525467ad00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=114c0b12d00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net: hsr: Reset MAC header for Tx path
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-05-09 15:16 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
2019-03-12 16:21 ` Dmitry Vyukov
2019-03-13 18:22 ` Oliver Hartkopp
2021-05-09 15:16 ` syzbot [this message]
2021-05-10 6:09 ` [syzbot] " 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=000000000000e5b92105c1e723d5@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=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=hch@lst.de \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--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 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.