From: syzbot <syzbot+fbf74291c3b7e753b481@syzkaller.appspotmail.com>
To: bigeasy@linutronix.de, davem@davemloft.net, edumazet@google.com,
hdanton@sina.com, kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] possible deadlock in hsr_dev_xmit (2)
Date: Sun, 05 May 2024 02:08:02 -0700 [thread overview]
Message-ID: <0000000000003bcdf30617b14ab6@google.com> (raw)
In-Reply-To: <000000000000c430800614b93936@google.com>
syzbot has bisected this issue to:
commit 06afd2c31d338fa762548580c1bf088703dd1e03
Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date: Tue Nov 29 16:48:12 2022 +0000
hsr: Synchronize sending frames to have always incremented outgoing seq nr.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=133c15f8980000
start commit: 5829614a7b3b Merge branch 'net-sysctl-sentinel'
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10bc15f8980000
console output: https://syzkaller.appspot.com/x/log.txt?x=173c15f8980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7c70a227bc928e1b
dashboard link: https://syzkaller.appspot.com/bug?extid=fbf74291c3b7e753b481
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=144d20e4980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1532ab38980000
Reported-by: syzbot+fbf74291c3b7e753b481@syzkaller.appspotmail.com
Fixes: 06afd2c31d33 ("hsr: Synchronize sending frames to have always incremented outgoing seq nr.")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-05-05 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 14:20 [syzbot] [net?] possible deadlock in hsr_dev_xmit (2) syzbot
2024-04-01 6:11 ` syzbot
2024-04-01 13:03 ` Hillf Danton
2024-04-01 13:36 ` syzbot
2024-04-01 22:44 ` Hillf Danton
2024-04-02 3:26 ` syzbot
2024-05-05 9:08 ` 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=0000000000003bcdf30617b14ab6@google.com \
--to=syzbot+fbf74291c3b7e753b481@syzkaller.appspotmail.com \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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