From: syzbot <syzbot+b8c48ea38ca27d150063@syzkaller.appspotmail.com>
To: andrew@lunn.ch, cratiu@nvidia.com, davem@davemloft.net,
edumazet@google.com, horms@kernel.org, jv@jvosburgh.net,
kuba@kernel.org, kuni1840@gmail.com, kuniyu@amazon.com,
kuniyu@google.com, linux-kernel@vger.kernel.org,
liuhangbin@gmail.com, netdev@vger.kernel.org, pabeni@redhat.com,
sdf@fomichev.me, stfomichev@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in __linkwatch_sync_dev (2)
Date: Sat, 02 Aug 2025 08:01:03 -0700 [thread overview]
Message-ID: <688e282f.050a0220.81582.0000.GAE@google.com> (raw)
In-Reply-To: <684a39aa.a00a0220.1eb5f5.00fa.GAE@google.com>
syzbot has bisected this issue to:
commit 04efcee6ef8d0f01eef495db047e7216d6e6e38f
Author: Stanislav Fomichev <sdf@fomichev.me>
Date: Fri Apr 4 16:11:22 2025 +0000
net: hold instance lock during NETDEV_CHANGE
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13eb22a2580000
start commit: afd8c2c9e2e2 Merge branch 'ipv6-f6i-fib6_siblings-and-rt-f..
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=101b22a2580000
console output: https://syzkaller.appspot.com/x/log.txt?x=17eb22a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a4bcc0a11b3192be
dashboard link: https://syzkaller.appspot.com/bug?extid=b8c48ea38ca27d150063
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11fa74a2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=117731bc580000
Reported-by: syzbot+b8c48ea38ca27d150063@syzkaller.appspotmail.com
Fixes: 04efcee6ef8d ("net: hold instance lock during NETDEV_CHANGE")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-08-02 15:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 2:21 syzbot
2025-06-13 1:09 ` Stanislav Fomichev
2025-06-13 23:56 ` Jakub Kicinski
2025-06-13 20:30 ` syzbot
2025-06-16 15:54 ` Stanislav Fomichev
2025-06-16 16:07 ` syzbot
2025-08-02 23:09 ` Hillf Danton
2025-08-02 23:28 ` syzbot
2025-08-02 15:01 ` 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=688e282f.050a0220.81582.0000.GAE@google.com \
--to=syzbot+b8c48ea38ca27d150063@syzkaller.appspotmail.com \
--cc=andrew@lunn.ch \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=stfomichev@gmail.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
all inboxes | Powered by JetHome®