From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org
Cc: asml.silence@gmail.com, axboe@kernel.dk, netdev@vger.kernel.org
Subject: [PATCH io_uring-7.1 v3 0/6] follow up zcrx fixes
Date: Tue, 31 Mar 2026 22:07:37 +0100 [thread overview]
Message-ID: <cover.1774780198.git.asml.silence@gmail.com> (raw)
Follow up fixes for the recent update flagged by review.
v3: include the mmap_offset cast patch from Anas
v2: reject REG_NODEV + ->rx_buf_size
Anas Iqbal (1):
io_uring: cast id to u64 before shifting in io_allocate_rbuf_ring()
Pavel Begunkov (5):
io_uring/zcrx: reject REG_NODEV with large rx_buf_size
io_uring/zcrx: don't use mark0 for allocating xarray
io_uring/zcrx: don't clear not allocated niovs
io_uring/zcrx: use dma_len for chunk size calculation
io_uring/zcrx: use correct mmap off constants
io_uring/zcrx.c | 18 +++++++++++-------
1 file changed, 11 insertions(+), 7 deletions(-)
--
2.53.0
next reply other threads:[~2026-03-31 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 21:07 Pavel Begunkov [this message]
2026-03-31 21:07 ` [PATCH io_uring-7.1 v3 1/6] io_uring/zcrx: reject REG_NODEV with large rx_buf_size Pavel Begunkov
2026-03-31 21:07 ` [PATCH io_uring-7.1 v3 2/6] io_uring: cast id to u64 before shifting in io_allocate_rbuf_ring() Pavel Begunkov
2026-03-31 21:07 ` [PATCH io_uring-7.1 v3 3/6] io_uring/zcrx: don't use mark0 for allocating xarray Pavel Begunkov
2026-03-31 21:07 ` [PATCH io_uring-7.1 v3 4/6] io_uring/zcrx: don't clear not allocated niovs Pavel Begunkov
2026-03-31 21:07 ` [PATCH io_uring-7.1 v3 5/6] io_uring/zcrx: use dma_len for chunk size calculation Pavel Begunkov
2026-03-31 21:07 ` [PATCH io_uring-7.1 v3 6/6] io_uring/zcrx: use correct mmap off constants Pavel Begunkov
2026-04-01 13:39 ` [PATCH io_uring-7.1 v3 0/6] follow up zcrx fixes Jens Axboe
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=cover.1774780198.git.asml.silence@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.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