From: <gregkh@linuxfoundation.org>
To: gregkh@linuxfoundation.org,matttbe@kernel.org,mptcp@lists.linux.dev
Cc: <stable-commits@vger.kernel.org>
Subject: Patch "selftests: mptcp: join: fix AF_INET6 variable" has been added to the 6.6-stable tree
Date: Thu, 13 Feb 2025 14:13:48 +0100 [thread overview]
Message-ID: <2025021348-grapple-junkyard-3bff@gregkh> (raw)
In-Reply-To: <20250209174153.3388802-8-matttbe@kernel.org>
This is a note to let you know that I've just added the patch titled
selftests: mptcp: join: fix AF_INET6 variable
to the 6.6-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-fix-af_inet6-variable.patch
and it can be found in the queue-6.6 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.
From stable+bounces-114457-greg=kroah.com@vger.kernel.org Sun Feb 9 18:42:17 2025
From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Date: Sun, 9 Feb 2025 18:41:57 +0100
Subject: selftests: mptcp: join: fix AF_INET6 variable
To: mptcp@lists.linux.dev, stable@vger.kernel.org, gregkh@linuxfoundation.org
Cc: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Message-ID: <20250209174153.3388802-8-matttbe@kernel.org>
From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
The Fixes commit is a backport renaming a variable, from AF_INET6 to
MPTCP_LIB_AF_INET6.
The commit has been applied without conflicts, except that it missed one
extra variable that was in v6.6, but not in the version linked to the
Fixes commit.
This variable has then been renamed too to avoid these errors:
LISTENER_CREATED 10.0.2.1:10100 ./mptcp_join.sh: line 2944: [: 2: unary operator expected
LISTENER_CLOSED 10.0.2.1:10100 ./mptcp_join.sh: line 2944: [: 2: unary operator expected
Fixes: a17d1419126b ("selftests: mptcp: declare event macros in mptcp_lib")
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
tools/testing/selftests/net/mptcp/mptcp_join.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
+++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
@@ -2941,7 +2941,7 @@ verify_listener_events()
type=$(mptcp_lib_evts_get_info type "$evt" "$e_type")
family=$(mptcp_lib_evts_get_info family "$evt" "$e_type")
sport=$(mptcp_lib_evts_get_info sport "$evt" "$e_type")
- if [ $family ] && [ $family = $AF_INET6 ]; then
+ if [ $family ] && [ $family = $MPTCP_LIB_AF_INET6 ]; then
saddr=$(mptcp_lib_evts_get_info saddr6 "$evt" "$e_type")
else
saddr=$(mptcp_lib_evts_get_info saddr4 "$evt" "$e_type")
Patches currently in stable-queue which might be from matttbe@kernel.org are
queue-6.6/mm-kmemleak-fix-upper-boundary-check-for-physical-address-objects.patch
queue-6.6/mptcp-prevent-excessive-coalescing-on-receive.patch
queue-6.6/selftests-mptcp-connect-f-no-reconnect.patch
queue-6.6/selftests-mptcp-join-fix-af_inet6-variable.patch
queue-6.6/mptcp-pm-only-set-fullmesh-for-subflow-endp.patch
prev parent reply other threads:[~2025-02-13 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 17:51 FAILED: patch "[PATCH] mptcp: pm: only set fullmesh for subflow endp" failed to apply to 6.6-stable tree gregkh
2025-02-09 17:41 ` [PATCH 6.6.y 0/3] mptcp: pm: only set fullmesh for subflow endp (and more) Matthieu Baerts (NGI0)
2025-02-09 17:41 ` [PATCH 6.6.y 1/3] mptcp: pm: only set fullmesh for subflow endp Matthieu Baerts (NGI0)
2025-02-13 13:13 ` Patch "mptcp: pm: only set fullmesh for subflow endp" has been added to the 6.6-stable tree gregkh
2025-02-09 17:41 ` [PATCH 6.6.y 2/3] mptcp: prevent excessive coalescing on receive Matthieu Baerts (NGI0)
2025-02-13 13:13 ` Patch "mptcp: prevent excessive coalescing on receive" has been added to the 6.6-stable tree gregkh
2025-02-09 17:41 ` [PATCH 6.6.y 3/3] selftests: mptcp: join: fix AF_INET6 variable Matthieu Baerts (NGI0)
2025-02-13 13:13 ` gregkh [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=2025021348-grapple-junkyard-3bff@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=stable-commits@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.