* [PATCH] io_uring/net: keep recvmsg buffer select length within MAX_RW_COUNT
@ 2026-10-23 11:22 Yichong Chen
2026-10-23 15:29 ` Jens Axboe
0 siblings, 1 reply; 2+ messages in thread
From: Yichong Chen @ 2026-10-23 11:22 UTC (permalink / raw)
To: Jens Axboe, io-uring; +Cc: linux-kernel, Stefan Metzmacher, Yichong Chen
io_recvmsg() takes the transfer length from the ring provided buffer when
sqe->len is 0, and such a buffer can be up to 4G. min_ret is an int, so 2G
or more makes it negative and the (ret < min_ret) block is skipped, and the
oversized length reaches the socket layer unchanged: an empty socket then
completes with 0 instead of arming poll, and a short read is reported as
complete. Clamp the length to MAX_RW_COUNT, as io_recv() does.
Fixes: 78d0d2063bab ("io_uring/net: disable partial retries for recvmsg with cmsg")
Signed-off-by: Yichong Chen <chenyichong@uniontech.com>
---
io_uring/net.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/io_uring/net.c b/io_uring/net.c
index eeab88e77fd8..4678f29f5177 100644
--- a/io_uring/net.c
+++ b/io_uring/net.c
@@ -1068,6 +1068,7 @@ int io_recvmsg(struct io_kiocb *req, unsigned int issue_flags)
sel = io_buffer_select(req, &len, sr->buf_group, issue_flags);
if (!sel.addr)
return -ENOBUFS;
+ len = min_t(size_t, len, MAX_RW_COUNT);
if (req->flags & REQ_F_APOLL_MULTISHOT) {
ret = io_recvmsg_prep_multishot(kmsg, sr, &sel.addr, &len);
--
2.51.0
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: [PATCH] io_uring/net: keep recvmsg buffer select length within MAX_RW_COUNT
2026-10-23 11:22 [PATCH] io_uring/net: keep recvmsg buffer select length within MAX_RW_COUNT Yichong Chen
@ 2026-10-23 15:29 ` Jens Axboe
0 siblings, 0 replies; 2+ messages in thread
From: Jens Axboe @ 2026-10-23 15:29 UTC (permalink / raw)
To: Yichong Chen, io-uring; +Cc: linux-kernel, Stefan Metzmacher
On 10/23/26 5:22 AM, Yichong Chen wrote:
> io_recvmsg() takes the transfer length from the ring provided buffer when
> sqe->len is 0, and such a buffer can be up to 4G. min_ret is an int, so 2G
> or more makes it negative and the (ret < min_ret) block is skipped, and the
> oversized length reaches the socket layer unchanged: an empty socket then
> completes with 0 instead of arming poll, and a short read is reported as
> complete. Clamp the length to MAX_RW_COUNT, as io_recv() does.
>
> Fixes: 78d0d2063bab ("io_uring/net: disable partial retries for recvmsg with cmsg")
Don't think that's correct, it just moved the check. Should be:
c7fb19428d67 ("io_uring: add support for ring mapped supplied buffers")
instead. I will fix that up. Waiting on Linus pulling the
previous bits, then I will queue this up for 7.4.
--
Jens Axboe
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-10-23 15:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-10-23 11:22 [PATCH] io_uring/net: keep recvmsg buffer select length within MAX_RW_COUNT Yichong Chen
2026-10-23 15:29 ` Jens Axboe
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®