From: Greg KH <gregkh@linuxfoundation.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
Mat Martineau <martineau@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
stable@vger.kernel.org, mptcp@lists.linux.dev
Subject: Re: [PATCH 6.6.y 2/4] selftests: mptcp: join: test for flush/re-add endpoints
Date: Wed, 4 Sep 2024 16:20:33 +0200 [thread overview]
Message-ID: <2024090428-jingle-railway-8ddd@gregkh> (raw)
In-Reply-To: <a5f25f18-d60f-4544-9f28-3a463911fd0b@kernel.org>
On Wed, Sep 04, 2024 at 02:59:07PM +0200, Matthieu Baerts wrote:
> Hi Greg, Sasha,
>
> On 03/09/2024 12:08, 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 recently queued all the patches from this series for
> v6.6, 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.6.
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2024-09-04 14:20 UTC|newest]
Thread overview: 8+ 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.6-stable tree gregkh
2024-09-03 10:08 ` [PATCH 6.6.y 0/4] Backport of "selftests: mptcp: join: test for flush/re-add endpoints" and more Matthieu Baerts (NGI0)
2024-09-03 10:08 ` [PATCH 6.6.y 1/4] selftests: mptcp: add explicit test case for remove/readd Matthieu Baerts (NGI0)
2024-09-03 10:08 ` [PATCH 6.6.y 2/4] selftests: mptcp: join: test for flush/re-add endpoints Matthieu Baerts (NGI0)
2024-09-04 12:59 ` Matthieu Baerts
2024-09-04 14:20 ` Greg KH [this message]
2024-09-03 10:08 ` [PATCH 6.6.y 3/4] selftests: mptcp: join: check re-using ID of unused ADD_ADDR Matthieu Baerts (NGI0)
2024-09-03 10:08 ` [PATCH 6.6.y 4/4] selftests: mptcp: join: check re-adding init endp with != id 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=2024090428-jingle-railway-8ddd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@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