From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: Paolo Abeni <pabeni@redhat.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next] Squash-to: "mptcp: more careful RM_ADDR generation"
Date: Tue, 22 Feb 2022 10:39:05 -0800 (PST) [thread overview]
Message-ID: <792f20dc-b820-25c-e38-d84c7c22194@linux.intel.com> (raw)
In-Reply-To: <5eea9634-7238-5dec-80e2-043d3cdead50@tessares.net>
On Tue, 22 Feb 2022, Matthieu Baerts wrote:
> Hi Paolo,
>
> On 21/02/2022 17:54, Paolo Abeni wrote:
>> When the self-tests flushed the subflows on both sides of
>> the MPTCP connections, the number of subflows actually deleted
>> on each side is unreliable.
>>
>> The test code always flushes first the client side, but the
>> actual delete operations is performed asynchronously, and one
>> on more subflows could be processed after that the other end
>> already deleted it.
>>
>> The grand total of the deleted subflows is expected to be
>> in the [nr_subflows: 2* nr_subflows] range.
>>
>> Address the issue checking the total number of deleted subflows
>> in the simult flush cases and enforcing the above constraint
>
> Thank you for the update!
>
> It is now in our tree, I hope that's OK for you Mat!
>
Yes, thanks for applying!
--
Mat Martineau
Intel
prev parent reply other threads:[~2022-02-22 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 16:54 [PATCH mptcp-next] Squash-to: "mptcp: more careful RM_ADDR generation" Paolo Abeni
2022-02-21 16:59 ` Matthieu Baerts
2022-02-22 11:00 ` Matthieu Baerts
2022-02-22 18:39 ` Mat Martineau [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=792f20dc-b820-25c-e38-d84c7c22194@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.