From: Constantine Gavrilov <CONSTG@il.ibm.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: io_uring_enter() with opcode IORING_OP_RECV ignores MSG_WAITALL in msg_flags
Date: Wed, 23 Mar 2022 12:11:38 +0000 [thread overview]
Message-ID: <DM6PR15MB2603BF2AA241ECB50ED6E167FA189@DM6PR15MB2603.namprd15.prod.outlook.com> (raw)
I get partial receives on TCP socket, even though I specify MSG_WAITALL
with IORING_OP_RECV opcode. Looking at tcpdump in wireshark, I see
entire reassambled packet (+4k), so it is not a disconnect. The MTU is
smaller than 4k.
From
the mailing list history, looks like this was discussed before and it
seems the fix was supposed to be in. Can someone clarify the expected
behavior?
I do not think rsvmsg() has this issue.
--
----------------------------------------
Constantine Gavrilov
Storage Architect
Master Inventor
Tel-Aviv IBM Storage Lab
1 Azrieli Center, Tel-Aviv
----------------------------------------
next reply other threads:[~2022-03-23 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 12:11 Constantine Gavrilov [this message]
[not found] <BYAPR15MB260078EC747F0F0183D1BB1BFA189@BYAPR15MB2600.namprd15.prod.outlook.com>
2022-03-23 12:19 ` io_uring_enter() with opcode IORING_OP_RECV ignores MSG_WAITALL in msg_flags Jens Axboe
2022-03-23 19:40 ` Pavel Begunkov
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=DM6PR15MB2603BF2AA241ECB50ED6E167FA189@DM6PR15MB2603.namprd15.prod.outlook.com \
--to=constg@il.ibm.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).