From: Nikolay Aleksandrov <razor@blackwall.org>
To: Daniel Borkmann <daniel@iogearbox.net>, kuba@kernel.org
Cc: ahmedabdelmoumen05@gmail.com, netdev@vger.kernel.org,
Bobby Eshleman <bobbyeshleman@meta.com>,
David Wei <dw@davidwei.uk>
Subject: Re: [PATCH net-next] net: Stop leased rxq before uninstalling its memory provider
Date: Wed, 10 Jun 2026 09:01:11 +0300 [thread overview]
Message-ID: <20eb0404-dd06-4845-aaaa-e157e120829a@blackwall.org> (raw)
In-Reply-To: <20260609212240.677889-1-daniel@iogearbox.net>
On 10/06/2026 00:22, Daniel Borkmann wrote:
> netif_rxq_cleanup_unlease() tears down the memory provider that was
> installed on a physical RX queue through a netkit queue lease. It
> currently revokes the provider's DMA mappings before stopping the
> physical queue:
>
> __netif_mp_uninstall_rxq(virt_rxq, p); /* DMA unmap */
> __netif_mp_close_rxq(phys_rxq->dev, rxq_idx, p); /* queue stop */
>
> This inverts the ordering used by the regular teardown paths (normal
> device unregister and the io_uring zcrx close path), which stop the
> queue before revoking the provider's mappings.
>
> With the physical queue still live, its NAPI can keep consuming
> net_iov entries from the page_pool alloc cache after the
> __netif_mp_uninstall_rxq() has already cleared their dma_addr,
> opening a window for the device to DMA to a stale or zero address.
>
> Fix it by swapping the two calls so the queue is stopped (and its
> NAPI quiesced) before the provider is uninstalled. No functional
> regression was observed across repeated runs of the nk_qlease.py
> HW selftest, which exercises the lease teardown path; this was
> tested against fbnic QEMU emulation.
>
> Fixes: 5602ad61ebee ("net: Proxy netif_mp_{open,close}_rxq for leased queues")
> Reported-by: Ahmed Abdelmoemen <ahmedabdelmoumen05@gmail.com>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> Cc: Bobby Eshleman <bobbyeshleman@meta.com>
> Cc: David Wei <dw@davidwei.uk>
> ---
> net/core/netdev_rx_queue.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/net/core/netdev_rx_queue.c b/net/core/netdev_rx_queue.c
> index de4dac4c88b3..00a7011eb4d5 100644
> --- a/net/core/netdev_rx_queue.c
> +++ b/net/core/netdev_rx_queue.c
> @@ -338,12 +338,12 @@ void __netif_mp_uninstall_rxq(struct netdev_rx_queue *rxq,
> void netif_rxq_cleanup_unlease(struct netdev_rx_queue *phys_rxq,
> struct netdev_rx_queue *virt_rxq)
> {
> - struct pp_memory_provider_params *p = &phys_rxq->mp_params;
> unsigned int rxq_idx = get_netdev_rx_queue_index(phys_rxq);
> + struct pp_memory_provider_params p = phys_rxq->mp_params;
>
> - if (!p->mp_ops)
> + if (!p.mp_ops)
> return;
>
> - __netif_mp_uninstall_rxq(virt_rxq, p);
> - __netif_mp_close_rxq(phys_rxq->dev, rxq_idx, p);
> + __netif_mp_close_rxq(phys_rxq->dev, rxq_idx, &p);
> + __netif_mp_uninstall_rxq(virt_rxq, &p);
> }
Reviewed-by: Nikolay Aleksandrov <razor@blackwall.org>
prev parent reply other threads:[~2026-06-10 6:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 21:22 [PATCH net-next] net: Stop leased rxq before uninstalling its memory provider Daniel Borkmann
2026-06-10 0:07 ` Bobby Eshleman
2026-06-10 6:01 ` Nikolay Aleksandrov [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=20eb0404-dd06-4845-aaaa-e157e120829a@blackwall.org \
--to=razor@blackwall.org \
--cc=ahmedabdelmoumen05@gmail.com \
--cc=bobbyeshleman@meta.com \
--cc=daniel@iogearbox.net \
--cc=dw@davidwei.uk \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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