From: patchwork-bot+netdevbpf@kernel.org
To: Carolina Jubran <cjubran@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, sdf@fomichev.me,
kuniyu@google.com, kory.maincent@bootlin.com, kees@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
cratiu@nvidia.com, dtatulea@nvidia.com
Subject: Re: [PATCH v2 net] net: dev_ioctl: take ops lock in hwtstamp lower paths
Date: Wed, 10 Sep 2025 01:30:06 +0000 [thread overview]
Message-ID: <175746780652.866782.7996733446987433045.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250907080821.2353388-1-cjubran@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 7 Sep 2025 11:08:21 +0300 you 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]
> 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>
> ....
>
> [...]
Here is the summary with links:
- [v2,net] net: dev_ioctl: take ops lock in hwtstamp lower paths
https://git.kernel.org/netdev/net/c/686cab5a18e4
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:[~2025-09-10 1:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 8:08 [PATCH v2 net] net: dev_ioctl: take ops lock in hwtstamp lower paths Carolina Jubran
2025-09-10 1:30 ` 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=175746780652.866782.7996733446987433045.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=kory.maincent@bootlin.com \
--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