From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next] mptcp: use fastclose on more edge scenarios.
Date: Mon, 29 Aug 2022 15:23:23 +0200 [thread overview]
Message-ID: <1455852631243eb21d13c86ba3ca2332a9bf48a3.camel@redhat.com> (raw)
In-Reply-To: <fda2e5ce19891d50fc3b7cff19c81330b5b475b1.1661533333.git.pabeni@redhat.com>
On Fri, 2022-08-26 at 19:03 +0200, Paolo Abeni wrote:
> Daire reported a user-space application hang-up when the
> peer is forcibly closed before the data transfer completion.
>
> The relevant application expects the peer to either
> do an application-level clean shutdown or a transport-level
> connection reset.
>
> We can accommodate a such user by extending the fastclose
> usage: at fd close time, if the msk socket has some unread
> data, and at FIN_WAIT timeout.
>
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
self-nack. This causes self-tests hang-up, even if the root cause of
the latter is likely pre-existent and this just uncover the latter
issue.
Will send a v2.
/P
prev parent reply other threads:[~2022-08-29 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 17:03 [PATCH mptcp-next] mptcp: use fastclose on more edge scenarios Paolo Abeni
2022-08-26 19:03 ` mptcp: use fastclose on more edge scenarios.: Tests Results MPTCP CI
2022-08-29 13:23 ` Paolo Abeni [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 \
--in-reply-to=1455852631243eb21d13c86ba3ca2332a9bf48a3.camel@redhat.com \
--to=pabeni@redhat.com \
--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).