From: syzbot <syzbot+3c47b5843403a45aef57@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, jiri@nvidia.com,
jiri@resnulli.us, kuba@kernel.org, linux-kernel@vger.kernel.org,
liuhangbin@gmail.com, netdev@vger.kernel.org,
nicolas.dichtel@6wind.com, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, xrivendell7@gmail.com
Subject: Re: [syzbot] [net?] possible deadlock in team_port_change_check (2)
Date: Wed, 06 Mar 2024 00:27:04 -0800 [thread overview]
Message-ID: <0000000000003fde310612f9b943@google.com> (raw)
In-Reply-To: <000000000000a97e9f061287624c@google.com>
syzbot has bisected this issue to:
commit ec4ffd100ffb396eca13ebe7d18938ea80f399c3
Author: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Date: Mon Jan 8 09:41:02 2024 +0000
Revert "net: rtnetlink: Enslave device before bringing it up"
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=163d5686180000
start commit: 90d35da658da Linux 6.8-rc7
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=153d5686180000
console output: https://syzkaller.appspot.com/x/log.txt?x=113d5686180000
kernel config: https://syzkaller.appspot.com/x/.config?x=c11c5c676adb61f0
dashboard link: https://syzkaller.appspot.com/bug?extid=3c47b5843403a45aef57
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=158ae1de180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=165f2732180000
Reported-by: syzbot+3c47b5843403a45aef57@syzkaller.appspotmail.com
Fixes: ec4ffd100ffb ("Revert "net: rtnetlink: Enslave device before bringing it up"")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-03-06 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 16:02 [syzbot] [net?] possible deadlock in team_port_change_check (2) syzbot
2024-02-29 16:58 ` Jiri Pirko
2024-03-05 22:44 ` syzbot
2024-03-07 9:26 ` Edward Adam Davis
2024-03-07 9:50 ` syzbot
2024-03-07 10:02 ` Edward Adam Davis
2024-03-07 10:48 ` syzbot
2024-03-06 8:27 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-02 13:52 xingwei lee
2024-03-03 8:39 xingwei lee
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=0000000000003fde310612f9b943@google.com \
--to=syzbot+3c47b5843403a45aef57@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@nvidia.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xrivendell7@gmail.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.