public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Stefan Metzmacher <[email protected]>, io-uring <[email protected]>
Subject: Re: [PATCH] io_uring/net: clear msg_controllen on partial sendmsg retry
Date: Tue, 20 Jun 2023 07:06:33 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 6/20/23 1:56?AM, Stefan Metzmacher wrote:
> Hi Jens,
> 
>> If we have cmsg attached AND we transferred partial data at least, clear
>> msg_controllen on retry so we don't attempt to send that again.
>>
>> Cc: [email protected] # 5.10+
>> Fixes: cac9e4418f4c ("io_uring/net: save msghdr->msg_control for retries")
>> 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 51b0f7fbb4f5..fe1c478c7dec 100644
>> --- a/io_uring/net.c
>> +++ b/io_uring/net.c
>> @@ -326,6 +326,7 @@ int io_sendmsg(struct io_kiocb *req, unsigned int issue_flags)
>>           if (ret == -EAGAIN && (issue_flags & IO_URING_F_NONBLOCK))
>>               return io_setup_async_msg(req, kmsg, issue_flags);
>>           if (ret > 0 && io_net_retry(sock, flags)) {
>> +            kmsg->msg.msg_controllen = 0;
>>               sr->done_io += ret;
>>               req->flags |= REQ_F_PARTIAL_IO;
>>               return io_setup_async_msg(req, kmsg, issue_flags);
>>
> 
> Should we also set 'kmsg->msg.msg_control' to NULL?

We could, but I don't think it matters as we gate any checks on that
anyway. But in terms of completeness, may as well I suppose.

-- 
Jens Axboe


      reply	other threads:[~2023-06-20 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 15:38 [PATCH] io_uring/net: clear msg_controllen on partial sendmsg retry Jens Axboe
2023-06-20  7:56 ` Stefan Metzmacher
2023-06-20 13:06   ` 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