From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf@fomichev.me>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, jv@jvosburgh.net,
andrew+netdev@lunn.ch, linux-kernel@vger.kernel.org,
liuhangbin@gmail.com,
syzbot+48c14f61594bdfadb086@syzkaller.appspotmail.com
Subject: Re: [PATCH net v2] bonding: hold ops lock around get_link
Date: Sat, 12 Apr 2025 02:01:31 +0000 [thread overview]
Message-ID: <174442329101.549857.7851201366120153854.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250410161117.3519250-1-sdf@fomichev.me>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 10 Apr 2025 09:11:17 -0700 you wrote:
> syzbot reports a case of ethtool_ops->get_link being called without
> ops lock:
>
> ethtool_op_get_link+0x15/0x60 net/ethtool/ioctl.c:63
> bond_check_dev_link+0x1fb/0x4b0 drivers/net/bonding/bond_main.c:864
> bond_miimon_inspect drivers/net/bonding/bond_main.c:2734 [inline]
> bond_mii_monitor+0x49d/0x3170 drivers/net/bonding/bond_main.c:2956
> process_one_work kernel/workqueue.c:3238 [inline]
> process_scheduled_works+0xac3/0x18e0 kernel/workqueue.c:3319
> worker_thread+0x870/0xd50 kernel/workqueue.c:3400
> kthread+0x7b7/0x940 kernel/kthread.c:464
> ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:153
> ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
>
> [...]
Here is the summary with links:
- [net,v2] bonding: hold ops lock around get_link
https://git.kernel.org/netdev/net/c/f7a11cba0ed7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-04-12 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 16:11 [PATCH net v2] bonding: hold ops lock around get_link Stanislav Fomichev
2025-04-12 2:01 ` patchwork-bot+netdevbpf [this message]
2025-04-27 3:06 ` Wang Liang
2025-04-28 2:02 ` Hangbin Liu
2025-04-28 15:10 ` Jay Vosburgh
2025-04-29 3:52 ` Hangbin Liu
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=174442329101.549857.7851201366120153854.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=syzbot+48c14f61594bdfadb086@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).