From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf@fomichev.me>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net v5 00/11] net: hold instance lock during NETDEV_UP/REGISTER
Date: Thu, 03 Apr 2025 22:50:33 +0000 [thread overview]
Message-ID: <174372063301.2709734.14320566471718210495.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250401163452.622454-1-sdf@fomichev.me>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 1 Apr 2025 09:34:41 -0700 you wrote:
> Solving the issue reported by Cosmin in [0] requires consistent
> lock during NETDEV_UP/REGISTER notifiers. This series
> addresses that (along with some other fixes in net/ipv4/devinet.c
> and net/ipv6/addrconf.c) and appends the patches from Jakub
> that were conditional on consistent locking in NETDEV_UNREGISTER.
>
> 0: https://lore.kernel.org/netdev/700fa36b94cbd57cfea2622029b087643c80cbc9.camel@nvidia.com/
>
> [...]
Here is the summary with links:
- [net,v5,01/11] net: switch to netif_disable_lro in inetdev_init
https://git.kernel.org/netdev/net/c/d2ccd0560d96
- [net,v5,02/11] net: hold instance lock during NETDEV_REGISTER/UP
https://git.kernel.org/netdev/net/c/4c975fd70002
- [net,v5,03/11] net: use netif_disable_lro in ipv6_add_dev
https://git.kernel.org/netdev/net/c/8965c160b8f7
- [net,v5,04/11] net: rename rtnl_net_debug to lock_debug
https://git.kernel.org/netdev/net/c/b912d599d3d8
- [net,v5,05/11] netdevsim: add dummy device notifiers
https://git.kernel.org/netdev/net/c/1901066aab76
- [net,v5,06/11] net: dummy: request ops lock
https://git.kernel.org/netdev/net/c/dbfc99495d96
- [net,v5,07/11] docs: net: document netdev notifier expectations
https://git.kernel.org/netdev/net/c/ee705fa21fdc
- [net,v5,08/11] selftests: net: use netdevsim in netns test
https://git.kernel.org/netdev/net/c/56c8a23f8a0f
- [net,v5,09/11] net: designate XSK pool pointers in queues as "ops protected"
(no matching commit)
- [net,v5,10/11] netdev: add "ops compat locking" helpers
(no matching commit)
- [net,v5,11/11] netdev: don't hold rtnl_lock over nl queue info get when possible
(no matching commit)
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-04-03 22:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 16:34 [PATCH net v5 00/11] net: hold instance lock during NETDEV_UP/REGISTER Stanislav Fomichev
2025-04-01 16:34 ` [PATCH net v5 01/11] net: switch to netif_disable_lro in inetdev_init Stanislav Fomichev
2025-04-01 16:34 ` [PATCH net v5 02/11] net: hold instance lock during NETDEV_REGISTER/UP Stanislav Fomichev
2025-04-03 0:02 ` Jakub Kicinski
2025-04-03 0:12 ` Jakub Kicinski
2025-04-03 2:34 ` Stanislav Fomichev
2025-04-01 16:34 ` [PATCH net v5 03/11] net: use netif_disable_lro in ipv6_add_dev Stanislav Fomichev
2025-04-01 16:34 ` [PATCH net v5 04/11] net: rename rtnl_net_debug to lock_debug Stanislav Fomichev
2025-04-01 16:34 ` [PATCH net v5 05/11] netdevsim: add dummy device notifiers Stanislav Fomichev
2025-04-01 16:34 ` [PATCH net v5 06/11] net: dummy: request ops lock Stanislav Fomichev
2025-04-01 16:34 ` [PATCH net v5 07/11] docs: net: document netdev notifier expectations Stanislav Fomichev
2025-04-01 16:34 ` [PATCH net v5 08/11] selftests: net: use netdevsim in netns test Stanislav Fomichev
2025-04-01 16:34 ` [PATCH net v5 09/11] net: designate XSK pool pointers in queues as "ops protected" Stanislav Fomichev
2025-04-01 16:34 ` [PATCH net v5 10/11] netdev: add "ops compat locking" helpers Stanislav Fomichev
2025-04-01 16:34 ` [PATCH net v5 11/11] netdev: don't hold rtnl_lock over nl queue info get when possible Stanislav Fomichev
2025-04-03 0:05 ` [PATCH net v5 00/11] net: hold instance lock during NETDEV_UP/REGISTER Jakub Kicinski
2025-04-03 22: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=174372063301.2709734.14320566471718210495.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.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;
as well as URLs for NNTP newsgroup(s).