From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Paul Chaignon <paul.chaignon@gmail.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH stable 5.10,5.15 2/2] bpf: Fix L4 csum update on IPv6 in CHECKSUM_COMPLETE
Date: Thu, 19 Jun 2025 05:02:46 -0400 [thread overview]
Message-ID: <20250618141007-b3db4a0bbd6a9834@stable.kernel.org> (raw)
In-Reply-To: <2ce92c476e4acba76002b69ad71093c5f8a681c6.1750171422.git.paul.chaignon@gmail.com>
[ 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: ead7f9b8de65632ef8060b84b0c55049a33cfea1
Status in newer kernel trees:
6.15.y | Present (different SHA1: 147c9e7472c9)
6.12.y | Not found
6.6.y | Not found
6.1.y | Not found
5.15.y | Not found
Note: The patch differs from the upstream commit:
---
1: ead7f9b8de656 < -: ------------- bpf: Fix L4 csum update on IPv6 in CHECKSUM_COMPLETE
-: ------------- > 1: ac4f00b960a0e net: Fix checksum update for ILA adj-transport
---
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-06-19 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 15:48 [PATCH stable 5.10,5.15 1/2] net: Fix checksum update for ILA adj-transport Paul Chaignon
2025-06-17 15:49 ` [PATCH stable 5.10,5.15 2/2] bpf: Fix L4 csum update on IPv6 in CHECKSUM_COMPLETE Paul Chaignon
2025-06-19 9:02 ` Sasha Levin [this message]
2025-06-23 8:46 ` Greg Kroah-Hartman
2025-06-23 9:04 ` Paul Chaignon
2025-06-23 9:13 ` Greg Kroah-Hartman
2025-06-19 9:04 ` [PATCH stable 5.10,5.15 1/2] net: Fix checksum update for ILA adj-transport 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=20250618141007-b3db4a0bbd6a9834@stable.kernel.org \
--to=sashal@kernel.org \
--cc=paul.chaignon@gmail.com \
--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