From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Jens Axboe <axboe@kernel.dk>, io-uring <io-uring@vger.kernel.org>
Cc: Sung Keum <kambodi127@gmail.com>
Subject: Re: [PATCH] io_uring/net: initialize mshot_len for send
Date: Sun, 26 Jul 2026 20:11:23 -0400 [thread overview]
Message-ID: <87y0excmvo.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <660d1bae-3e03-4ed7-b26b-86e22722e51c@kernel.dk>
Jens Axboe <axboe@kernel.dk> writes:
> Commit:
>
> 6a8afb9fff64 ("io_uring/net: allow multishot receive per-invocation cap")
>
> changed how io_mshot_prep_retry() set sr->len, and added the same
> initialization in io_mshot_prep_retry(). But it neglected to touch the
> send path, which may also uses the mshot retry path. Ensure that
> sr->mshot_len always gets initialized correctly.
>
> Fixes: 6a8afb9fff64 ("io_uring/net: allow multishot receive per-invocation cap")
> Cc: stable@vger.kernel.org
> Reported-by: Sung Keum <kambodi127@gmail.com>
> Signed-off-by: Jens Axboe <axboe@kernel.dk>
>
Reviewed-by: Gabriel Krisman Bertazi <krisman@suse.de>
--
Gabriel Krisman Bertazi
prev parent reply other threads:[~2026-07-27 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 22:27 [PATCH] io_uring/net: initialize mshot_len for send Jens Axboe
2026-07-27 0:11 ` Gabriel Krisman Bertazi [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=87y0excmvo.fsf@mailhost.krisman.be \
--to=krisman@suse.de \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=kambodi127@gmail.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