Netdev List
 help / color / mirror / Atom feed
From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
	andrew+netdev@lunn.ch, horms@kernel.org, andrew@lunn.ch,
	gal@nvidia.com, jacob.e.keller@intel.com, sdf@fomichev.me,
	kory.maincent@bootlin.com
Subject: Re: [PATCH net-next] ethtool: tsconfig: always take rtnl_lock
Date: Thu, 11 Jun 2026 23:25:06 +0100	[thread overview]
Message-ID: <0b9a7503-f54e-458b-ab09-0fbc831d9f76@linux.dev> (raw)
In-Reply-To: <20260611200355.2020663-1-kuba@kernel.org>

On 11/06/2026 21:03, Jakub Kicinski wrote:
> mlx5 throws ASSERT_RTNL() warnings on timestamp config, because
> it tries to update features. mlx5e_hwtstamp_set() calls
> netdev_update_features().
> 
> I missed this while grepping the drivers because tsconfig goes
> through ndo_hwtstamp_set/get, not ethtool ops, even tho the new
> uAPI is in ethtool Netlink. We could add a dedicated opt out bit
> for mlx5, but NDOs were not supposed to be part of the ethtool locking
> conversion in the first place.
> 
> The mlx5 features update is related to the "compressed CQE" format
> which lacks timestamp, apparently. See commit c0194e2d0ef0 ("net/mlx5e:
> Disable rxhash when CQE compress is enabled").
> 
> Fixes: 6e9e2eed4f39 ("net: ethtool: Add support for tsconfig command to get/set hwtstamp config")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: andrew@lunn.ch
> CC: gal@nvidia.com
> CC: jacob.e.keller@intel.com
> CC: sdf@fomichev.me
> CC: kory.maincent@bootlin.com
> ---
>   net/ethtool/common.h | 7 +++++++
>   1 file changed, 7 insertions(+)
> 
> diff --git a/net/ethtool/common.h b/net/ethtool/common.h
> index e3052972f953..2b3847f00801 100644
> --- a/net/ethtool/common.h
> +++ b/net/ethtool/common.h
> @@ -113,6 +113,13 @@ ethtool_nl_msg_needs_rtnl(const struct net_device *dev, u8 cmd)
>   		return ops->op_needs_rtnl & ETHTOOL_OP_NEEDS_RTNL_SPAUSEPARAM;
>   	case ETHTOOL_MSG_RSS_SET:
>   		return ops->op_needs_rtnl & ETHTOOL_OP_NEEDS_RTNL_RSS;
> +	case ETHTOOL_MSG_TSCONFIG_GET:
> +	case ETHTOOL_MSG_TSCONFIG_SET:
> +		/* tsconfig calls ndos (ndo_hwtstamp_set/get), not ethtool ops.
> +		 * Also, there is no corresponding ethtool ioctl, therefore
> +		 * these cases are Netlink-only.
> +		 */
> +		return true;
>   	}
>   	return false;
>   }

Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>

      parent reply	other threads:[~2026-06-11 22:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11 20:03 [PATCH net-next] ethtool: tsconfig: always take rtnl_lock Jakub Kicinski
2026-06-11 20:05 ` Jakub Kicinski
2026-06-11 20:05   ` Jakub Kicinski
2026-06-11 20:24 ` Stanislav Fomichev
2026-06-11 20:55 ` Jacob Keller
2026-06-11 22:25 ` Vadim Fedorenko [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=0b9a7503-f54e-458b-ab09-0fbc831d9f76@linux.dev \
    --to=vadim.fedorenko@linux.dev \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=horms@kernel.org \
    --cc=jacob.e.keller@intel.com \
    --cc=kory.maincent@bootlin.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    /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