public inbox for [email protected]
 help / color / mirror / Atom feed
From: Stefan Metzmacher <[email protected]>
To: Jens Axboe <[email protected]>, io-uring <[email protected]>
Subject: Re: [PATCH v2] io_uring/net: disable partial retries for recvmsg with cmsg
Date: Wed, 21 Jun 2023 13:34:01 +0200	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Am 20.06.23 um 15:19 schrieb Jens Axboe:
> We cannot sanely handle partial retries for recvmsg if we have cmsg
> attached. If we don't, then we'd just be overwriting the initial cmsg
> header on retries. Alternatively we could increment and handle this
> appropriately, but it doesn't seem worth the complication.
> 
> Move the MSG_WAITALL check into the non-multishot case while at it,
> since MSG_WAITALL is explicitly disabled for multishot anyway.
> 
> Link: https://lore.kernel.org/io-uring/[email protected]/
> Cc: [email protected] # 5.10+
> Reported-by: Stefan Metzmacher <[email protected]>
> Signed-off-by: Jens Axboe <[email protected]>

Also Reviewed-by: Stefan Metzmacher <[email protected]>

> ---
> 
> v2: correct msg_controllen check and move into non-mshot branch
> 
>   io_uring/net.c | 11 +++++++----
>   1 file changed, 7 insertions(+), 4 deletions(-)
> 
> diff --git a/io_uring/net.c b/io_uring/net.c
> index c0924ab1ea11..2bc2cb2f4d6c 100644
> --- a/io_uring/net.c
> +++ b/io_uring/net.c
> @@ -789,16 +789,19 @@ int io_recvmsg(struct io_kiocb *req, unsigned int issue_flags)
>   	flags = sr->msg_flags;
>   	if (force_nonblock)
>   		flags |= MSG_DONTWAIT;
> -	if (flags & MSG_WAITALL)
> -		min_ret = iov_iter_count(&kmsg->msg.msg_iter);
>   
>   	kmsg->msg.msg_get_inq = 1;
> -	if (req->flags & REQ_F_APOLL_MULTISHOT)
> +	if (req->flags & REQ_F_APOLL_MULTISHOT) {
>   		ret = io_recvmsg_multishot(sock, sr, kmsg, flags,
>   					   &mshot_finished);
> -	else
> +	} else {
> +		/* disable partial retry for recvmsg with cmsg attached */
> +		if (flags & MSG_WAITALL && !kmsg->msg.msg_controllen)
> +			min_ret = iov_iter_count(&kmsg->msg.msg_iter);
> +
>   		ret = __sys_recvmsg_sock(sock, &kmsg->msg, sr->umsg,
>   					 kmsg->uaddr, flags);
> +	}
>   
>   	if (ret < min_ret) {
>   		if (ret == -EAGAIN && force_nonblock) {


      reply	other threads:[~2023-06-21 11:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20 13:19 [PATCH v2] io_uring/net: disable partial retries for recvmsg with cmsg Jens Axboe
2023-06-21 11:34 ` Stefan Metzmacher [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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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