From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
michael.chan@broadcom.com, hkallweit1@gmail.com,
maxime.chevallier@bootlin.com, joshwash@google.com,
tariqt@nvidia.com, alexanderduyck@fb.com, willemb@google.com,
jacob.e.keller@intel.com, kory.maincent@bootlin.com,
sdf.kernel@gmail.com, jakub@cloudflare.com, nb@tipi-net.de
Subject: Re: [PATCH net-next v2 00/12] net: ethtool: let ops locked drivers run without rtnl_lock
Date: Tue, 09 Jun 2026 17:40:21 +0000 [thread overview]
Message-ID: <178102682114.2158043.6852117340367698479.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260605002912.3456868-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 4 Jun 2026 17:29:00 -0700 you wrote:
> With the ethtool_get_link_ksettings() situation hopefully ironed out
> the previous series (commit 6a5d837f0ce2) let's return to the main
> part of the series.
>
> We have been slowly moving towards removing the rtnl_lock dependency
> in driver ops since the concept of "ops-locked" drivers have been
> introduced last year. Since last year will take the netdev instance
> lock before invoking any ndo or ethtool op of "ops-locked" drivers.
>
> [...]
Here is the summary with links:
- [net-next,v2,01/12] net: ethtool: serialize broadcast notification sequence allocation
https://git.kernel.org/netdev/net-next/c/8845484367da
- [net-next,v2,02/12] net: ethtool: relax ethnl_req_get_phydev() locking assertion
https://git.kernel.org/netdev/net-next/c/ded86da4bbb7
- [net-next,v2,03/12] net: ethtool: make dev->hwprov ops-protected
https://git.kernel.org/netdev/net-next/c/97f51bf91b3a
- [net-next,v2,04/12] net: ethtool: optionally skip rtnl_lock on Netlink path for GET ops
https://git.kernel.org/netdev/net-next/c/45079e00133e
- [net-next,v2,05/12] net: ethtool: optionally skip rtnl_lock on Netlink path for SET ops
https://git.kernel.org/netdev/net-next/c/f9a3e05114b8
- [net-next,v2,06/12] net: ethtool: optionally skip rtnl_lock in cable test handlers
https://git.kernel.org/netdev/net-next/c/f16013fde46d
- [net-next,v2,07/12] net: ethtool: optionally skip rtnl_lock in ethnl_tsinfo_dumpit()
https://git.kernel.org/netdev/net-next/c/0c334c21f5a5
- [net-next,v2,08/12] net: ethtool: optionally skip rtnl_lock in ethnl_act_module_fw_flash()
https://git.kernel.org/netdev/net-next/c/2526717624ab
- [net-next,v2,09/12] net: ethtool: optionally skip rtnl_lock in RSS context handlers
https://git.kernel.org/netdev/net-next/c/732fa5ced1cc
- [net-next,v2,10/12] net: ethtool: ioctl: concentrate the locking
https://git.kernel.org/netdev/net-next/c/f58a40d07be3
- [net-next,v2,11/12] net: ethtool: optionally skip rtnl_lock on IOCTL path
https://git.kernel.org/netdev/net-next/c/f994752b1127
- [net-next,v2,12/12] docs: net: ethtool: document ops-locked drivers and op_needs_rtnl
https://git.kernel.org/netdev/net-next/c/b5125db8d020
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-09 17:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 0:29 [PATCH net-next v2 00/12] net: ethtool: let ops locked drivers run without rtnl_lock Jakub Kicinski
2026-06-05 0:29 ` [PATCH net-next v2 01/12] net: ethtool: serialize broadcast notification sequence allocation Jakub Kicinski
2026-06-09 15:32 ` Eric Dumazet
2026-06-05 0:29 ` [PATCH net-next v2 02/12] net: ethtool: relax ethnl_req_get_phydev() locking assertion Jakub Kicinski
2026-06-09 15:33 ` Eric Dumazet
2026-06-05 0:29 ` [PATCH net-next v2 03/12] net: ethtool: make dev->hwprov ops-protected Jakub Kicinski
2026-06-09 15:35 ` Eric Dumazet
2026-06-05 0:29 ` [PATCH net-next v2 04/12] net: ethtool: optionally skip rtnl_lock on Netlink path for GET ops Jakub Kicinski
2026-06-09 15:37 ` Eric Dumazet
2026-06-05 0:29 ` [PATCH net-next v2 05/12] net: ethtool: optionally skip rtnl_lock on Netlink path for SET ops Jakub Kicinski
2026-06-08 22:15 ` Jacob Keller
2026-06-08 23:58 ` Jakub Kicinski
2026-06-09 1:01 ` Jacob Keller
2026-06-09 15:40 ` Eric Dumazet
2026-06-05 0:29 ` [PATCH net-next v2 06/12] net: ethtool: optionally skip rtnl_lock in cable test handlers Jakub Kicinski
2026-06-08 22:17 ` Jacob Keller
2026-06-09 15:41 ` Eric Dumazet
2026-06-05 0:29 ` [PATCH net-next v2 07/12] net: ethtool: optionally skip rtnl_lock in ethnl_tsinfo_dumpit() Jakub Kicinski
2026-06-09 15:42 ` Eric Dumazet
2026-06-05 0:29 ` [PATCH net-next v2 08/12] net: ethtool: optionally skip rtnl_lock in ethnl_act_module_fw_flash() Jakub Kicinski
2026-06-09 15:43 ` Eric Dumazet
2026-06-05 0:29 ` [PATCH net-next v2 09/12] net: ethtool: optionally skip rtnl_lock in RSS context handlers Jakub Kicinski
2026-06-09 15:44 ` Eric Dumazet
2026-06-05 0:29 ` [PATCH net-next v2 10/12] net: ethtool: ioctl: concentrate the locking Jakub Kicinski
2026-06-09 15:46 ` Eric Dumazet
2026-06-05 0:29 ` [PATCH net-next v2 11/12] net: ethtool: optionally skip rtnl_lock on IOCTL path Jakub Kicinski
2026-06-09 15:49 ` Eric Dumazet
2026-06-05 0:29 ` [PATCH net-next v2 12/12] docs: net: ethtool: document ops-locked drivers and op_needs_rtnl Jakub Kicinski
2026-06-09 15:50 ` Eric Dumazet
2026-06-05 22:48 ` [PATCH net-next v2 00/12] net: ethtool: let ops locked drivers run without rtnl_lock Stanislav Fomichev
2026-06-06 0:09 ` Jakub Kicinski
2026-06-08 15:20 ` Stanislav Fomichev
2026-06-08 22:04 ` Jacob Keller
2026-06-08 22:31 ` Jacob Keller
2026-06-08 23:01 ` Jacob Keller
2026-06-08 23:33 ` Tony Nguyen
2026-06-09 1:44 ` Jakub Kicinski
2026-06-09 17:40 ` patchwork-bot+netdevbpf [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=178102682114.2158043.6852117340367698479.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=jakub@cloudflare.com \
--cc=joshwash@google.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=michael.chan@broadcom.com \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf.kernel@gmail.com \
--cc=tariqt@nvidia.com \
--cc=willemb@google.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