Netdev List
 help / color / mirror / Atom feed
From: Jakub Sitnicki <jakub@cloudflare.com>
To: Nicolai Buchwitz <nb@tipi-net.de>
Cc: Jakub Kicinski <kuba@kernel.org>,
	 davem@davemloft.net, netdev@vger.kernel.org,
	 edumazet@google.com,  pabeni@redhat.com, andrew+netdev@lunn.ch,
	 horms@kernel.org,  michael.chan@broadcom.com,
	joshwash@google.com,  tariqt@nvidia.com,  haiyangz@microsoft.com,
	linux@armlinux.org.uk,  maxime.chevallier@bootlin.com,
	willemb@google.com,  ernis@linux.microsoft.com,
	 sdf.kernel@gmail.com, kory.maincent@bootlin.com,
	 danieller@nvidia.com,  idosch@nvidia.com
Subject: Re: [PATCH net-next 02/14] net: ethtool: make sure __ethtool_get_link_ksettings() is ops-locked
Date: Tue, 02 Jun 2026 13:35:33 +0200	[thread overview]
Message-ID: <874ijl5g56.fsf@cloudflare.com> (raw)
In-Reply-To: <34fad14a092e28c3512f2405f0869133@tipi-net.de> (Nicolai Buchwitz's message of "Tue, 02 Jun 2026 13:20:30 +0200")

On Tue, Jun 02, 2026 at 01:20 PM +02, Nicolai Buchwitz wrote:
> Hi Jakub ^ 2
>
> On 2.6.2026 11:17, Jakub Sitnicki wrote:
>> On Thu, May 28, 2026 at 04:16 PM -07, Jakub Kicinski wrote:
>>> __ethtool_get_link_ksettings() is exported and called from sysfs
>>> and many drivers. Looks like commit 2bcf4772e45a ("net: ethtool:
>>> try to protect all callback with netdev instance lock")
>>> missed adding the lock around it. Not treating this as a fix because
>>> I don't think any driver cares at this point, but if we want to
>>> remove the rtnl_lock protection this will become critical.
>>> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>
>> [...]
>
>>> diff --git a/net/ethtool/ioctl.c b/net/ethtool/ioctl.c
>
>> [...]
>
>>>  /* Internal kernel helper to query a device ethtool_link_settings. */
>>> -int __ethtool_get_link_ksettings(struct net_device *dev,
>>> -				 struct ethtool_link_ksettings *link_ksettings)
>>> +int ethtool_get_link_ksettings_locked(struct net_device *dev,
>>> +				      struct ethtool_link_ksettings *link_ksettings)
>>>  {
>>> -	ASSERT_RTNL();
>>> +	netdev_ops_assert_locked(dev);
>> Not sure why we're using the "compat" assertion here, which falls back
>> to check if RTNL is held, instead of the newly introduced
>> netdev_assert_locked_if_ops().
>> The contract here is that all callers are expected to hold the
>> netdev lock (if needed), IIUC.
>> [...]
>
> AFAIU that's on purpose: the original helper had ASSERT_RTNL(), and
> legacy callers still enter with rtnl_lock via the wrapper. _if_ops
> would silently pass for them if rtnl ever went missing.

But the legacy callers continue using __ethtool_get_link_ksettings(),
which has an explicit ASSERT_RTNL(), so I still don't get it:

| +/* Convenience helper for callers that hold only rtnl_lock(). */
| +int __ethtool_get_link_ksettings(struct net_device *dev,
| +				 struct ethtool_link_ksettings *link_ksettings)
| +{
| +	int ret;
| +
| +	ASSERT_RTNL();
| +
| +	netdev_lock_ops(dev);
| +	ret = ethtool_get_link_ksettings_locked(dev, link_ksettings);
| +	netdev_unlock_ops(dev);
| +	return ret;
| +}
|  EXPORT_SYMBOL(__ethtool_get_link_ksettings);

Anyway, no sense speculating. Let's wait for Jakub.

  reply	other threads:[~2026-06-02 11:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28 23:16 [PATCH net-next 00/14] net: ethtool: let ops locked drivers run without rtnl_lock Jakub Kicinski
2026-05-28 23:16 ` [PATCH net-next 01/14] net: ethtool: cmis_cdb: hold instance lock for ops locked devices Jakub Kicinski
2026-05-29 11:25   ` Jakub Sitnicki
2026-05-28 23:16 ` [PATCH net-next 02/14] net: ethtool: make sure __ethtool_get_link_ksettings() is ops-locked Jakub Kicinski
2026-06-02  9:17   ` Jakub Sitnicki
2026-06-02 11:20     ` Nicolai Buchwitz
2026-06-02 11:35       ` Jakub Sitnicki [this message]
2026-05-28 23:16 ` [PATCH net-next 03/14] net: ethtool: serialize broadcast notification sequence allocation Jakub Kicinski
2026-05-28 23:16 ` [PATCH net-next 04/14] net: ethtool: relax ethnl_req_get_phydev() locking assertion Jakub Kicinski
2026-05-29  8:43   ` Maxime Chevallier
2026-05-29 14:27     ` Jakub Kicinski
2026-06-02 11:07     ` Nicolai Buchwitz
2026-05-28 23:16 ` [PATCH net-next 05/14] net: ethtool: make dev->hwprov ops-protected Jakub Kicinski
2026-05-28 23:16 ` [PATCH net-next 06/14] net: ethtool: optionally skip rtnl_lock on Netlink path for GET ops Jakub Kicinski
2026-05-28 23:16 ` [PATCH net-next 07/14] net: ethtool: optionally skip rtnl_lock on Netlink path for SET ops Jakub Kicinski
2026-05-28 23:16 ` [PATCH net-next 08/14] net: ethtool: optionally skip rtnl_lock in cable test handlers Jakub Kicinski
2026-05-28 23:16 ` [PATCH net-next 09/14] net: ethtool: optionally skip rtnl_lock in ethnl_tsinfo_dumpit() Jakub Kicinski
2026-05-28 23:16 ` [PATCH net-next 10/14] net: ethtool: optionally skip rtnl_lock in ethnl_act_module_fw_flash() Jakub Kicinski
2026-05-28 23:16 ` [PATCH net-next 11/14] net: ethtool: optionally skip rtnl_lock in RSS context handlers Jakub Kicinski
2026-05-28 23:16 ` [PATCH net-next 12/14] net: ethtool: ioctl: concentrate the locking Jakub Kicinski
2026-05-28 23:16 ` [PATCH net-next 13/14] net: ethtool: optionally skip rtnl_lock on IOCTL path Jakub Kicinski
2026-06-01 15:17   ` Stanislav Fomichev
2026-06-01 19:10     ` Jakub Kicinski
2026-05-28 23:16 ` [PATCH net-next 14/14] docs: net: ethtool: document ops-locked drivers and op_needs_rtnl Jakub Kicinski
2026-06-02 10:57   ` Nicolai Buchwitz
2026-05-29  7:41 ` [syzbot ci] Re: net: ethtool: let ops locked drivers run without rtnl_lock syzbot ci

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=874ijl5g56.fsf@cloudflare.com \
    --to=jakub@cloudflare.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=danieller@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=ernis@linux.microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=joshwash@google.com \
    --cc=kory.maincent@bootlin.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --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