public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: mptcp@lists.linux.dev, Mat Martineau <martineau@kernel.org>,
	Geliang Tang <geliang@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Gang Yan <yangang@kylinos.cn>,
	Davide Caratti <dcaratti@redhat.com>
Subject: Re: [PATCH net-next 0/4] mptcp: various small improvements
Date: Wed, 30 Oct 2024 18:07:36 +0100	[thread overview]
Message-ID: <66de4e7f-96bc-461b-81ca-5182d55308b1@kernel.org> (raw)
In-Reply-To: <20241029165016.568f01bd@kernel.org>

Hi Jakub,

On 30/10/2024 00:50, Jakub Kicinski wrote:
> On Mon, 21 Oct 2024 17:14:02 +0200 Matthieu Baerts (NGI0) wrote:
>> The following patches are not related to each other.
>>
>> - Patch 1: Avoid sending advertisements on stale subflows, reducing
>>   risks on loosing them.
>>
>> - Patch 2: Annotate data-races around subflow->fully_established, using
>>   READ/WRITE_ONCE().
>>
>> - Patch 3: A small clean-up on the PM side, avoiding a bit of duplicated
>>   code.
>>
>> - Patch 4: Use "Middlebox interference" MP_TCPRST code in reaction to a
>>   packet received without MPTCP options in the middle of a connection.
> 
> Could be a coincidence but looks like we got two flakes in mptcp-join
> since yesterday (different sub-cases).

Thank you for having reported this. It looks like a coincidence, but I
will monitor that.

> What's more sad is that it looks
> like our subcase parsing is broken, when I look at the subcase view
> all sub-cases are marked as passing :( Could you take a look?

I think the issue is with the 'retry' feature, when the nested tests are
parsed. I hope I fixed this in:

  https://github.com/linux-netdev/nipa/pull/43

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


      reply	other threads:[~2024-10-30 17:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 15:14 [PATCH net-next 0/4] mptcp: various small improvements Matthieu Baerts (NGI0)
2024-10-21 15:14 ` [PATCH net-next 1/4] mptcp: pm: send ACK on non-stale subflows Matthieu Baerts (NGI0)
2024-10-21 15:14 ` [PATCH net-next 2/4] mptcp: annotate data-races around subflow->fully_established Matthieu Baerts (NGI0)
2024-10-25  9:55   ` Simon Horman
2024-10-25 15:52     ` Matthieu Baerts
2024-10-21 15:14 ` [PATCH net-next 3/4] mptcp: implement mptcp_pm_connection_closed Matthieu Baerts (NGI0)
2024-10-21 15:14 ` [PATCH net-next 4/4] mptcp: use "middlebox interference" RST when no DSS Matthieu Baerts (NGI0)
2024-10-28 23:00 ` [PATCH net-next 0/4] mptcp: various small improvements patchwork-bot+netdevbpf
2024-10-29 23:50 ` Jakub Kicinski
2024-10-30 17:07   ` Matthieu Baerts [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=66de4e7f-96bc-461b-81ca-5182d55308b1@kernel.org \
    --to=matttbe@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dcaratti@redhat.com \
    --cc=edumazet@google.com \
    --cc=geliang@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martineau@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=yangang@kylinos.cn \
    /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