From: Jens Axboe <[email protected]>
To: Stefan Metzmacher <[email protected]>, io-uring <[email protected]>
Subject: Re: [PATCH] io_uring/net: disable partial retries for recvmsg with cmsg
Date: Tue, 20 Jun 2023 07:05:07 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/20/23 2:26?AM, Stefan Metzmacher wrote:
> Hi Jens,
>
>> 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.
>>
>> 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]>
>>
>> ---
>>
>> diff --git a/io_uring/net.c b/io_uring/net.c
>> index fe1c478c7dec..6674a0759390 100644
>> --- a/io_uring/net.c
>> +++ b/io_uring/net.c
>> @@ -788,7 +788,8 @@ 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)
>> + /* disable partial retry for recvmsg with cmsg attached */
>> + if (flags & MSG_WAITALL && !kmsg->controllen)
>> min_ret = iov_iter_count(&kmsg->msg.msg_iter);
>
> Isn't kmsg->controllen only used for REQ_F_APOLL_MULTISHOT?
>
> I guess the correct value would be kmsg->msg.msg_controllen?
Gah, yes indeed it should!
> Maybe the safest change would be something like this (completely untested!):
>
> diff --git a/io_uring/net.c b/io_uring/net.c
> index 89e839013837..1dd5322fb732 100644
> --- a/io_uring/net.c
> +++ b/io_uring/net.c
> @@ -781,14 +781,14 @@ 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)
> ret = io_recvmsg_multishot(sock, sr, kmsg, flags,
> &mshot_finished);
> else
> + 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);
I like putting it there, as MSG_WAITALL is explicitly disallowed for
multishot anyway. The check belongs in that branch rather than as a
whole.
--
Jens Axboe
prev parent reply other threads:[~2023-06-20 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 15:43 [PATCH] io_uring/net: disable partial retries for recvmsg with cmsg Jens Axboe
2023-06-20 8:26 ` Stefan Metzmacher
2023-06-20 13:05 ` Jens Axboe [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