From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Daniel Borkmann <daniel@iogearbox.net>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH stable 6.1 3/3] veth: Use tstats per-CPU traffic counters
Date: Fri, 6 Dec 2024 18:11:49 -0500 [thread overview]
Message-ID: <20241206131424-437113d3ff8659e4@stable.kernel.org> (raw)
In-Reply-To: <20241206153403.273068-3-daniel@iogearbox.net>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 6f2684bf2b4460c84d0d34612a939f78b96b03fc
WARNING: Author mismatch between patch and upstream commit:
Backport author: Daniel Borkmann <daniel@iogearbox.net>
Commit author: Peilin Ye <peilin.ye@bytedance.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: b74095a4945f)
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
Failed to apply patch cleanly, falling back to interdiff...
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2024-12-06 23:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 15:34 [PATCH stable 6.1 1/3] net: Move {l,t,d}stats allocation to core and convert veth & vrf Daniel Borkmann
2024-12-06 15:34 ` [PATCH stable 6.1 2/3] bpf: Fix dev's rx stats for bpf_redirect_peer traffic Daniel Borkmann
2024-12-06 23:11 ` Sasha Levin
2024-12-06 15:34 ` [PATCH stable 6.1 3/3] veth: Use tstats per-CPU traffic counters Daniel Borkmann
2024-12-06 23:11 ` Sasha Levin [this message]
2024-12-06 23:11 ` [PATCH stable 6.1 1/3] net: Move {l,t,d}stats allocation to core and convert veth & vrf 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=20241206131424-437113d3ff8659e4@stable.kernel.org \
--to=sashal@kernel.org \
--cc=daniel@iogearbox.net \
--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