From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10.y 2/3] mptcp: only inc MPJoinAckHMacFailure for HMAC failures
Date: Sat, 19 Apr 2025 07:50:40 -0400 [thread overview]
Message-ID: <20250418203326-98252d9a1f423c86@stable.kernel.org> (raw)
In-Reply-To: <20250418164556.3926588-7-matttbe@kernel.org>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 21c02e8272bc95ba0dd44943665c669029b42760
Status in newer kernel trees:
6.14.y | Present (different SHA1: f41db9f7222f)
6.13.y | Present (different SHA1: ee6cece8b2ca)
6.12.y | Present (different SHA1: 711bc4864e66)
6.6.y | Present (different SHA1: 440cc72ac34d)
6.1.y | Present (different SHA1: f92899f0301c)
5.15.y | Present (different SHA1: 738aefd9d94f)
Note: The patch differs from the upstream commit:
---
1: 21c02e8272bc9 < -: ------------- mptcp: only inc MPJoinAckHMacFailure for HMAC failures
-: ------------- > 1: 97a808168f008 mptcp: only inc MPJoinAckHMacFailure for HMAC failures
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
next prev parent reply other threads:[~2025-04-19 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 16:45 [PATCH 5.10.y 0/3] mptcp: fix recent failed backports Matthieu Baerts (NGI0)
2025-04-18 16:45 ` [PATCH 5.10.y 1/3] mptcp: fix NULL pointer in can_accept_new_subflow Matthieu Baerts (NGI0)
2025-04-19 11:50 ` Sasha Levin
2025-04-18 16:45 ` [PATCH 5.10.y 2/3] mptcp: only inc MPJoinAckHMacFailure for HMAC failures Matthieu Baerts (NGI0)
2025-04-19 11:50 ` Sasha Levin [this message]
2025-04-18 16:46 ` [PATCH 5.10.y 3/3] mptcp: sockopt: fix getting IPV6_V6ONLY Matthieu Baerts (NGI0)
2025-04-19 11:46 ` 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=20250418203326-98252d9a1f423c86@stable.kernel.org \
--to=sashal@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 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.