public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
	Greg KH <gregkh@linuxfoundation.org>,
	Mat Martineau <martineau@kernel.org>
Subject: Re: Patch "selftests: mptcp: join: ability to invert ADD_ADDR check" has been added to the 6.10-stable tree
Date: Sun, 11 Aug 2024 17:20:50 -0400	[thread overview]
Message-ID: <ZrkrMu55FR9ROhsQ@sashalap> (raw)
In-Reply-To: <7180dcdb-694f-4014-9828-8baced3bfa7a@kernel.org>

On Sun, Aug 11, 2024 at 05:46:22PM +0200, Matthieu Baerts wrote:
>Hi Sasha, Greg,
>
>On 11/08/2024 14:56, Sasha Levin wrote:
>> This is a note to let you know that I've just added the patch titled
>>
>>     selftests: mptcp: join: ability to invert ADD_ADDR check
>>
>> to the 6.10-stable tree which can be found at:
>>     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>
>> The filename of the patch is:
>>      selftests-mptcp-join-ability-to-invert-add_addr-chec.patch
>> and it can be found in the queue-6.10 subdirectory.
>>
>> If you, or anyone else, feels it should not be added to the stable tree,
>> please let <stable@vger.kernel.org> know about it.
>>
>>
>>
>> commit 469e6fe99988649029b7f136218d5c3d8854e705
>> Author: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>> Date:   Wed Jul 31 13:05:58 2024 +0200
>>
>>     selftests: mptcp: join: ability to invert ADD_ADDR check
>>
>>     [ Upstream commit bec1f3b119ebc613d08dfbcdbaef01a79aa7de92 ]
>>
>>     In the following commit, the client will initiate the ADD_ADDR, instead
>>     of the server. We need to way to verify the ADD_ADDR have been correctly
>>     sent.
>>
>>     Note: the default expected counters for when the port number is given
>>     are never changed by the caller, no need to accept them as parameter
>>     then.
>>
>>     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.
>
>Sorry, I just realised I forgot to add the "Cc: Stable" on all patches
>from this series :-/
>
>This patch and "selftests: mptcp: join: test both signal & subflow"
>should be backported with the other patches modifying files in
>net/mptcp. Without them, the two patches that have just been added to
>the queue will just make the selftests failing.
>
>Is it then possible to drop these two patches from the 6.10, 6.6 and 6.1
>queues for the moment please? I can send patches for these versions
>later on.
>
>  selftests-mptcp-join-ability-to-invert-add_addr-chec.patch: 6.10, 6.6
>  selftests-mptcp-join-test-both-signal-subflow.patch: 6.10, 6.6 and 6.1

Sure, now dropped.

-- 
Thanks,
Sasha

      reply	other threads:[~2024-08-11 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240811125614.1262228-1-sashal@kernel.org>
2024-08-11 15:46 ` Patch "selftests: mptcp: join: ability to invert ADD_ADDR check" has been added to the 6.10-stable tree Matthieu Baerts
2024-08-11 21:20   ` Sasha Levin [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=ZrkrMu55FR9ROhsQ@sashalap \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=martineau@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=stable-commits@vger.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