From: Jakub Kicinski <kuba@kernel.org>
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: <almasrymina@google.com>, <asml.silence@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
<cratiu@nvidia.com>, <parav@nvidia.com>, <netdev@vger.kernel.org>,
<sdf@meta.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v5 6/7] net: devmem: pre-read requested rx queues during bind
Date: Tue, 26 Aug 2025 17:33:21 -0700 [thread overview]
Message-ID: <20250826173321.4ad50edc@kernel.org> (raw)
In-Reply-To: <20250825063655.583454-7-dtatulea@nvidia.com>
On Mon, 25 Aug 2025 09:36:38 +0300 Dragos Tatulea wrote:
> + rxq_idx = nla_get_u32(tb[NETDEV_A_QUEUE_ID]);
> + if (rxq_idx >= rxq_bitmap_len)
> + return -EINVAL;
Sorry, missed this in v4, could you add NL_SET_BAD_ATTR() here?
next prev parent reply other threads:[~2025-08-27 0:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 6:36 [PATCH net-next v5 0/7] devmem/io_uring: allow more flexibility for ZC DMA devices Dragos Tatulea
2025-08-25 6:36 ` [PATCH net-next v5 1/7] queue_api: add support for fetching per queue DMA dev Dragos Tatulea
2025-08-25 6:36 ` [PATCH net-next v5 2/7] io_uring/zcrx: add support for custom DMA devices Dragos Tatulea
2025-08-25 6:36 ` [PATCH net-next v5 3/7] net: devmem: get netdev DMA device via new API Dragos Tatulea
2025-08-25 6:36 ` [PATCH net-next v5 4/7] net/mlx5e: add op for getting netdev DMA device Dragos Tatulea
2025-08-25 6:36 ` [PATCH net-next v5 5/7] net: devmem: pull out dma_dev out of net_devmem_bind_dmabuf Dragos Tatulea
2025-08-25 6:36 ` [PATCH net-next v5 6/7] net: devmem: pre-read requested rx queues during bind Dragos Tatulea
2025-08-27 0:33 ` Jakub Kicinski [this message]
2025-08-27 14:34 ` Dragos Tatulea
2025-08-25 6:36 ` [PATCH net-next v5 7/7] net: devmem: allow binding on rx queues with same DMA devices Dragos Tatulea
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=20250826173321.4ad50edc@kernel.org \
--to=kuba@kernel.org \
--cc=almasrymina@google.com \
--cc=asml.silence@gmail.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=sdf@meta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®