From: Sasha Levin <sashal@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: Geliang Tang <geliang@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
stable@vger.kernel.org, Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 5.15.y] selftests: mptcp: connect: also cover alt modes
Date: Tue, 29 Jul 2025 10:36:55 -0400 [thread overview]
Message-ID: <aIjch3KtJoQFwaF-@lappy> (raw)
In-Reply-To: <ce3d987f-047a-4b5d-a2e9-f924e0700b15@kernel.org>
On Tue, Jul 29, 2025 at 04:32:21PM +0200, Matthieu Baerts wrote:
>Hi Sasha,
>
>On 29/07/2025 16:20, Sasha Levin wrote:
>> From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
>>
>> [ Upstream commit 37848a456fc38c191aedfe41f662cc24db8c23d9 ]
>>
>> The "mmap" and "sendfile" alternate modes for mptcp_connect.sh/.c are
>> available from the beginning, but only tested when mptcp_connect.sh is
>> manually launched with "-m mmap" or "-m sendfile", not via the
>> kselftests helpers.
>>
>> The MPTCP CI was manually running "mptcp_connect.sh -m mmap", but not
>> "-m sendfile". Plus other CIs, especially the ones validating the stable
>> releases, were not validating these alternate modes.
>>
>> To make sure these modes are validated by these CIs, add two new test
>> programs executing mptcp_connect.sh with the alternate modes.
>>
>> Fixes: 048d19d444be ("mptcp: add basic kselftest for mptcp")
>> Cc: stable@vger.kernel.org
>> Reviewed-by: Geliang Tang <geliang@kernel.org>
>> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>> Link: https://patch.msgid.link/20250715-net-mptcp-sft-connect-alt-v2-1-8230ddd82454@kernel.org
>> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>> [ Drop userspace_pm.sh from TEST_PROGS ]
>
>Thank you for having fixed the conflicts.
>
>Is it possible to hold this one for the moment? Yesterday, I was looking
>at this conflict, and when testing the same resolution as yours, I
>noticed mptcp_connect_sendfile.sh was failing on v5.15.y. I will
>investigate that.
>
>Please also note that this patch here will conflict with another you
>sent a few hours ago:
>
> https://lore.kernel.org/20250729034856.2353329-1-sashal@kernel.org
>
>When the issues are fixed, I can send both of them again if that's OK
>for you.
Thats perfect, I'll skip backports for there. Thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-07-29 14:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 13:48 FAILED: patch "[PATCH] selftests: mptcp: connect: also cover alt modes" failed to apply to 5.15-stable tree gregkh
2025-07-29 14:20 ` [PATCH 5.15.y] selftests: mptcp: connect: also cover alt modes Sasha Levin
2025-07-29 14:32 ` Matthieu Baerts
2025-07-29 14:36 ` Sasha Levin [this message]
2025-07-30 10:28 ` [PATCH 5.15.y 0/3] mptcp: fix recent failed backports (20250728) Matthieu Baerts (NGI0)
2025-07-30 10:28 ` [PATCH 5.15.y 1/3] selftests: mptcp: make sendfile selftest work Matthieu Baerts (NGI0)
2025-07-30 16:28 ` Sasha Levin
2025-07-30 10:28 ` [PATCH 5.15.y 2/3] selftests: mptcp: connect: also cover alt modes Matthieu Baerts (NGI0)
2025-07-30 16:28 ` Sasha Levin
2025-07-30 16:41 ` Matthieu Baerts
2025-07-31 1:09 ` Sasha Levin
2025-07-31 9:28 ` Matthieu Baerts
2025-07-30 10:28 ` [PATCH 5.15.y 3/3] selftests: mptcp: connect: also cover checksum Matthieu Baerts (NGI0)
2025-07-30 16:28 ` Sasha Levin
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=aIjch3KtJoQFwaF-@lappy \
--to=sashal@kernel.org \
--cc=geliang@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=matttbe@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