From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org, ap420073@gmail.com,
almasrymina@google.com, asml.silence@gmail.com, dw@davidwei.uk,
sdf@fomichev.me, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net v2 0/2] net: make memory provider install / close paths more common
Date: Wed, 2 Apr 2025 18:34:03 -0700 [thread overview]
Message-ID: <20250403013405.2827250-1-kuba@kernel.org> (raw)
We seem to be fixing bugs in config path for devmem which also exist
in the io_uring ZC path. Let's try to make the two paths more common,
otherwise this is bound to keep happening.
Found by code inspection and compile tested only.
v2:
- [patch 1] add to commit msg
- [patch 1] fix arg naming in the header
- [patch 2] don't split the registration check, it may cause a race
if we just bail on the registration state and not on the MP being
present, as we drop and re-take the instance lock after setting
reg_state
v1: https://lore.kernel.org/20250331194201.2026422-1-kuba@kernel.org
Jakub Kicinski (2):
net: move mp dev config validation to __net_mp_open_rxq()
net: avoid false positive warnings in __net_mp_close_rxq()
include/net/page_pool/memory_provider.h | 6 +++
net/core/devmem.c | 64 +++++++------------------
net/core/netdev-genl.c | 6 ---
net/core/netdev_rx_queue.c | 53 +++++++++++++++-----
4 files changed, 63 insertions(+), 66 deletions(-)
--
2.49.0
next reply other threads:[~2025-04-03 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 1:34 Jakub Kicinski [this message]
2025-04-03 1:34 ` [PATCH net v2 1/2] net: move mp dev config validation to __net_mp_open_rxq() Jakub Kicinski
2025-04-03 1:34 ` [PATCH net v2 2/2] net: avoid false positive warnings in __net_mp_close_rxq() Jakub Kicinski
2025-04-03 21:37 ` Mina Almasry
2025-04-04 15:10 ` [PATCH net v2 0/2] net: make memory provider install / close paths more common patchwork-bot+netdevbpf
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=20250403013405.2827250-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=ap420073@gmail.com \
--cc=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=horms@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 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.