From: Paolo Abeni <pabeni@redhat.com>
To: Benjamin Hesmans <benjamin.hesmans@tessares.net>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v1 3/5] mptcp: handle defer connect in mptcp_sendmsg
Date: Wed, 21 Sep 2022 19:41:24 +0200 [thread overview]
Message-ID: <199358242e294a6463cb4f785fb3c5c54603bb8f.camel@redhat.com> (raw)
In-Reply-To: <20220921152539.1851441-4-benjamin.hesmans@tessares.net>
Hello,
On Wed, 2022-09-21 at 17:25 +0200, Benjamin Hesmans wrote:
> When TCP_FASTOPEN_CONNECT has been set on the socket before a connect,
> the defer flag is set and must be handled when sendmsg is called.
>
> This is similar to what is done in tcp_sendmsg_locked().
>
> Signed-off-by: Benjamin Hesmans <benjamin.hesmans@tessares.net>
> ---
>
> Notes:
> v1:
> - error case use latest patch from Paolo (propagate fastclose error)
> - I believe the use __mptcp_nmpc_socket(msk); is correct here (instead of
> msk->first but would be nice is someone can confirm
Yep, AFAICS it's correct.
And patch LGTM.
Cheers,
Paolo
next prev parent reply other threads:[~2022-09-21 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 15:25 [PATCH mptcp-next v1 0/5] mptcp: add support for TFO, sender side only Benjamin Hesmans
2022-09-21 15:25 ` [PATCH mptcp-next v1 1/5] mptcp: add TCP_FASTOPEN_CONNECT socket option Benjamin Hesmans
2022-09-21 15:25 ` [PATCH mptcp-next v1 2/5] tcp: export tcp_sendmsg_fastopen Benjamin Hesmans
2022-09-21 15:25 ` [PATCH mptcp-next v1 3/5] mptcp: handle defer connect in mptcp_sendmsg Benjamin Hesmans
2022-09-21 17:41 ` Paolo Abeni [this message]
2022-09-21 15:25 ` [PATCH mptcp-next v1 4/5] mptcp: add MSG_FASTOPEN support Benjamin Hesmans
2022-09-21 15:25 ` [PATCH mptcp-next v1 5/5] mptcp: poll allow write call before actual connect Benjamin Hesmans
2022-09-21 16:52 ` mptcp: poll allow write call before actual connect: Tests Results MPTCP CI
2022-09-21 17:43 ` [PATCH mptcp-next v1 5/5] mptcp: poll allow write call before actual connect Paolo Abeni
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=199358242e294a6463cb4f785fb3c5c54603bb8f.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=benjamin.hesmans@tessares.net \
--cc=mptcp@lists.linux.dev \
/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).