From: patchwork-bot+netdevbpf@kernel.org
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, jacob.e.keller@intel.com,
sdf@fomichev.me, tariqt@nvidia.com, shshitrit@nvidia.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: Defer netdev KOBJ_ADD uevent until the device is published
Date: Thu, 06 Aug 2026 16:50:29 +0000 [thread overview]
Message-ID: <178603502963.1375455.13217677789461225888.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260806080758.2039586-2-dtatulea@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 6 Aug 2026 11:07:58 +0300 you wrote:
> netdev_register_kobject() calls device_add(), which emits KOBJ_ADD and
> wakes udev, but register_netdevice() only makes the device findable by
> name later, in list_netdevice(). A udev worker that reacts to the uevent
> can therefore run against a device that no lookup can find yet.
>
> This used to be harmless because the ethtool ioctl took the rtnl_lock
> when looking the device up, and register_netdevice() runs under rtnl, so
> the worker simply blocked until registration finished. The commit in the
> fixes tag moved the lookup out from under rtnl for ops-locked drivers.
> Now there is a short window in register_netdevice() between
> netdev_register_kobject() until list_netdevice() when the device is not
> findable by name.
>
> [...]
Here is the summary with links:
- [net,v2] net: Defer netdev KOBJ_ADD uevent until the device is published
https://git.kernel.org/netdev/net/c/8e63c9e6179a
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-08-06 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 8:07 [PATCH net v2] net: Defer netdev KOBJ_ADD uevent until the device is published Dragos Tatulea
2026-08-06 16:50 ` 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=178603502963.1375455.13217677789461225888.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shshitrit@nvidia.com \
--cc=tariqt@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.