From: Jens Axboe <axboe@kernel.dk>
To: David Wei <dw@davidwei.uk>, io-uring@vger.kernel.org
Cc: Pavel Begunkov <asml.silence@gmail.com>
Subject: Re: [PATCH] io_uring/zcrx: return early from io_zcrx_recv_skb if readlen is 0
Date: Tue, 1 Apr 2025 12:56:44 -0600 [thread overview]
Message-ID: <e89aef50-7364-4ab9-9582-aef6aec8cffb@kernel.dk> (raw)
In-Reply-To: <20250401182813.1115909-1-dw@davidwei.uk>
On 4/1/25 12:28 PM, David Wei wrote:
> When readlen is set for a recvzc request, tcp_read_sock() will call
> io_zcrx_recv_skb() one final time with len == desc->count == 0. This is
> caused by the !desc->count check happening too late. The offset + 1 !=
> skb->len happens earlier and causes the while loop to continue.
>
> Fix this in io_zcrx_recv_skb() instead of tcp_read_sock(). Return early
> if len is 0 i.e. the read is done.
Needs a Fixes tag, which looks like it should be:
Fixes: 6699ec9a23f8 ("io_uring/zcrx: add a read limit to recvzc requests")
?
> Signed-off-by: David Wei <dw@davidwei.uk>
> ---
> io_uring/zcrx.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/io_uring/zcrx.c b/io_uring/zcrx.c
> index 9c95b5b6ec4e..d1dd25e7cf4a 100644
> --- a/io_uring/zcrx.c
> +++ b/io_uring/zcrx.c
> @@ -818,6 +818,8 @@ io_zcrx_recv_skb(read_descriptor_t *desc, struct sk_buff *skb,
> int ret = 0;
>
> len = min_t(size_t, len, desc->count);
> + if (!len)
> + goto out;
just return 0 here? Jumping to out would make more sense if there
are things to fixup/account at this point, but it's just going
to find offset == start_off and return 'ret', which is 0 anyway.
--
Jens Axboe
next prev parent reply other threads:[~2025-04-01 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 18:28 [PATCH] io_uring/zcrx: return early from io_zcrx_recv_skb if readlen is 0 David Wei
2025-04-01 18:56 ` Jens Axboe [this message]
2025-04-01 19:10 ` David Wei
2025-04-01 19:12 ` 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=e89aef50-7364-4ab9-9582-aef6aec8cffb@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=dw@davidwei.uk \
--cc=io-uring@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