From: syzbot <syzbot+b8c48ea38ca27d150063@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, horms@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [net?] WARNING in __linkwatch_sync_dev (2)
Date: Wed, 11 Jun 2025 19:21:30 -0700 [thread overview]
Message-ID: <684a39aa.a00a0220.1eb5f5.00fa.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: f09079bd04a9 Merge tag 'powerpc-6.16-2' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16e9260c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e24211089078d6c6
dashboard link: https://syzkaller.appspot.com/bug?extid=b8c48ea38ca27d150063
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-f09079bd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ef68cb3d29a3/vmlinux-f09079bd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1cc9431b9a15/bzImage-f09079bd.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b8c48ea38ca27d150063@syzkaller.appspotmail.com
------------[ cut here ]------------
RTNL: assertion failed at ./include/net/netdev_lock.h (72)
WARNING: CPU: 0 PID: 1141 at ./include/net/netdev_lock.h:72 netdev_ops_assert_locked include/net/netdev_lock.h:72 [inline]
WARNING: CPU: 0 PID: 1141 at ./include/net/netdev_lock.h:72 __linkwatch_sync_dev+0x1ed/0x230 net/core/link_watch.c:279
Modules linked in:
CPU: 0 UID: 0 PID: 1141 Comm: kworker/u32:5 Not tainted 6.16.0-rc1-syzkaller-00003-gf09079bd04a9 #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Workqueue: bond0 bond_mii_monitor
RIP: 0010:netdev_ops_assert_locked include/net/netdev_lock.h:72 [inline]
RIP: 0010:__linkwatch_sync_dev+0x1ed/0x230 net/core/link_watch.c:279
Code: 05 ff ff ff e8 64 d1 59 f8 c6 05 76 2e 2e 07 01 90 ba 48 00 00 00 48 c7 c6 c0 88 e3 8c 48 c7 c7 60 88 e3 8c e8 64 96 18 f8 90 <0f> 0b 90 90 e9 d6 fe ff ff 48 c7 c7 44 3e a8 90 e8 fe 8e c0 f8 e9
RSP: 0018:ffffc900064a79f0 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff8880368fc000 RCX: ffffffff817ae368
RDX: ffff88802990a440 RSI: ffffffff817ae375 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: 1ffff92000c94f48
R13: ffff8880368fccc5 R14: ffffffff8c5909c0 R15: ffffffff899b8950
FS: 0000000000000000(0000) GS:ffff8880d6754000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555560fdf808 CR3: 000000000e382000 CR4: 0000000000352ef0
DR0: 0000000010000007 DR1: 400000000000000c DR2: 0000000000000000
DR3: 0000000000000005 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ethtool_op_get_link+0x1d/0x70 net/ethtool/ioctl.c:63
bond_check_dev_link+0x3f9/0x710 drivers/net/bonding/bond_main.c:863
bond_miimon_inspect drivers/net/bonding/bond_main.c:2745 [inline]
bond_mii_monitor+0x3c0/0x2dc0 drivers/net/bonding/bond_main.c:2967
process_one_work+0x9cf/0x1b70 kernel/workqueue.c:3238
process_scheduled_works kernel/workqueue.c:3321 [inline]
worker_thread+0x6c8/0xf10 kernel/workqueue.c:3402
kthread+0x3c5/0x780 kernel/kthread.c:464
ret_from_fork+0x5d4/0x6f0 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
next reply other threads:[~2025-06-12 2:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 2:21 syzbot [this message]
2025-06-13 1:09 ` [syzbot] [net?] WARNING in __linkwatch_sync_dev (2) 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
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=684a39aa.a00a0220.1eb5f5.00fa.GAE@google.com \
--to=syzbot+b8c48ea38ca27d150063@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--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 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.