From: Kory Maincent <kory.maincent@bootlin.com>
To: Carolina Jubran <cjubran@nvidia.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>,
Kuniyuki Iwashima <kuniyu@google.com>,
Kees Cook <kees@kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Cosmin Ratiu <cratiu@nvidia.com>,
Dragos Tatulea <dtatulea@nvidia.com>
Subject: Re: [PATCH net] net: dev_ioctl: take ops lock in hwtstamp lower paths
Date: Thu, 4 Sep 2025 23:52:25 +0200 [thread overview]
Message-ID: <20250904235155.7b2b3379@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <20250904182806.2329996-1-cjubran@nvidia.com>
On Thu, 4 Sep 2025 21:28:06 +0300
Carolina Jubran <cjubran@nvidia.com> wrote:
> ndo hwtstamp callbacks are expected to run under the per-device ops
> lock. Make the lower get/set paths consistent with the rest of ndo
> invocations.
>
> Kernel log:
> WARNING: CPU: 13 PID: 51364 at ./include/net/netdev_lock.h:70
> __netdev_update_features+0x4bd/0xe60 ...
> RIP: 0010:__netdev_update_features+0x4bd/0xe60
> ...
> Call Trace:
> <TASK>
> netdev_update_features+0x1f/0x60
> mlx5_hwtstamp_set+0x181/0x290 [mlx5_core]
> mlx5e_hwtstamp_set+0x19/0x30 [mlx5_core]
Where does these two functions come from? They are not mainline.
Else LGTM.
> dev_set_hwtstamp_phylib+0x9f/0x220
> dev_set_hwtstamp_phylib+0x9f/0x220
> dev_set_hwtstamp+0x13d/0x240
> dev_ioctl+0x12f/0x4b0
> sock_ioctl+0x171/0x370
> __x64_sys_ioctl+0x3f7/0x900
> ? __sys_setsockopt+0x69/0xb0
> do_syscall_64+0x6f/0x2e0
> entry_SYSCALL_64_after_hwframe+0x4b/0x53
> ...
> </TASK>
> ....
> ---[ end trace 0000000000000000 ]---
>
> Fixes: ffb7ed19ac0a ("net: hold netdev instance lock during ioctl operations")
> Signed-off-by: Carolina Jubran <cjubran@nvidia.com>
> Reviewed-by: Cosmin Ratiu <cratiu@nvidia.com>
> Reviewed-by: Dragos Tatulea <dtatulea@nvidia.com>
>
> ---
> net/core/dev_ioctl.c | 22 ++++++++++++++++++----
> 1 file changed, 18 insertions(+), 4 deletions(-)
>
> diff --git a/net/core/dev_ioctl.c b/net/core/dev_ioctl.c
> index 9c0ad7f4b5d8..ad54b12d4b4c 100644
> --- a/net/core/dev_ioctl.c
> +++ b/net/core/dev_ioctl.c
> @@ -464,8 +464,15 @@ int generic_hwtstamp_get_lower(struct net_device *dev,
> if (!netif_device_present(dev))
> return -ENODEV;
>
> - if (ops->ndo_hwtstamp_get)
> - return dev_get_hwtstamp_phylib(dev, kernel_cfg);
> + if (ops->ndo_hwtstamp_get) {
> + int err;
> +
> + netdev_lock_ops(dev);
> + err = dev_get_hwtstamp_phylib(dev, kernel_cfg);
> + netdev_unlock_ops(dev);
> +
> + return err;
> + }
>
> /* Legacy path: unconverted lower driver */
> return generic_hwtstamp_ioctl_lower(dev, SIOCGHWTSTAMP, kernel_cfg);
> @@ -481,8 +488,15 @@ int generic_hwtstamp_set_lower(struct net_device *dev,
> if (!netif_device_present(dev))
> return -ENODEV;
>
> - if (ops->ndo_hwtstamp_set)
> - return dev_set_hwtstamp_phylib(dev, kernel_cfg, extack);
> + if (ops->ndo_hwtstamp_set) {
> + int err;
> +
> + netdev_lock_ops(dev);
> + err = dev_set_hwtstamp_phylib(dev, kernel_cfg, extack);
> + netdev_unlock_ops(dev);
> +
> + return err;
> + }
>
> /* Legacy path: unconverted lower driver */
> return generic_hwtstamp_ioctl_lower(dev, SIOCSHWTSTAMP, kernel_cfg);
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-09-04 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 18:28 [PATCH net] net: dev_ioctl: take ops lock in hwtstamp lower paths Carolina Jubran
2025-09-04 21:52 ` Kory Maincent [this message]
2025-09-05 5:35 ` Carolina Jubran
2025-09-05 13:07 ` Simon Horman
2025-09-05 23:27 ` Jakub Kicinski
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=20250904235155.7b2b3379@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--cc=cjubran@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.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