From: Matthieu Baerts <matttbe@kernel.org>
To: gregkh@linuxfoundation.org
Cc: Mat Martineau <martineau@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
mptcp@lists.linux.dev, stable@vger.kernel.org,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.10.y 2/6] selftests: mptcp: join: test for flush/re-add endpoints
Date: Wed, 4 Sep 2024 14:40:52 +0200 [thread overview]
Message-ID: <1311d6a3-2007-4b26-aade-6c181ff67372@kernel.org> (raw)
In-Reply-To: <20240902172516.3021978-10-matttbe@kernel.org>
Hi Greg, Sasha,
On 02/09/2024 19:25, Matthieu Baerts (NGI0) wrote:
> commit e06959e9eebdfea4654390f53b65cff57691872e upstream.
>
> After having flushed endpoints that didn't cause the creation of new
> subflows, it is important to check endpoints can be re-created, re-using
> previously used IDs.
>
> Before the previous commit, the client would not have been able to
> re-create the subflow that was previously rejected.
>
> The 'Fixes' tag here below is the same as the one from the previous
> commit: this patch here is not fixing anything wrong in the selftests,
> but it validates the previous fix for an issue introduced by this commit
> ID.
FYI, Sasha has applied all the patches from this series, except this
one, the backport of e06959e9eebd ("selftests: mptcp: join: test for
flush/re-add endpoints").
In theory, this commit can be applied without any conflicts now that
commit b5e2fb832f48 ("selftests: mptcp: add explicit test case for
remove/readd") has been queued in v6.10.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-09-04 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 12:09 FAILED: patch "[PATCH] selftests: mptcp: join: test for flush/re-add endpoints" failed to apply to 6.10-stable tree gregkh
2024-09-02 17:25 ` [PATCH 6.10.y 0/6] Backport of "selftests: mptcp: join: test for flush/re-add endpoints" and more Matthieu Baerts (NGI0)
2024-09-02 17:25 ` [PATCH 6.10.y 1/6] selftests: mptcp: add explicit test case for remove/readd Matthieu Baerts (NGI0)
2024-09-02 17:25 ` [PATCH 6.10.y 2/6] selftests: mptcp: join: test for flush/re-add endpoints Matthieu Baerts (NGI0)
2024-09-04 12:40 ` Matthieu Baerts [this message]
2024-09-04 14:16 ` Greg KH
2024-09-02 17:25 ` [PATCH 6.10.y 3/6] selftests: mptcp: join: check re-using ID of unused ADD_ADDR Matthieu Baerts (NGI0)
2024-09-02 17:25 ` [PATCH 6.10.y 4/6] selftests: mptcp: join: check re-adding init endp with != id Matthieu Baerts (NGI0)
2024-09-02 17:25 ` [PATCH 6.10.y 5/6] selftests: mptcp: join: validate event numbers Matthieu Baerts (NGI0)
2024-09-02 17:25 ` [PATCH 6.10.y 6/6] selftests: mptcp: join: check re-re-adding ID 0 signal Matthieu Baerts (NGI0)
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=1311d6a3-2007-4b26-aade-6c181ff67372@kernel.org \
--to=matttbe@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=martineau@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@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