From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Shung-Hsi Yu <shung-hsi.yu@suse.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH stable 6.6 04/10] selftests/bpf: test for changing packet data from global functions
Date: Thu, 1 May 2025 15:11:43 -0400 [thread overview]
Message-ID: <20250501085413-c3dc132b416533b6@stable.kernel.org> (raw)
In-Reply-To: <20250430081955.49927-5-shung-hsi.yu@suse.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: 3f23ee5590d9605dbde9a5e1d4b97637a4803329
WARNING: Author mismatch between patch and upstream commit:
Backport author: Shung-Hsi Yu<shung-hsi.yu@suse.com>
Commit author: Eduard Zingerman<eddyz87@gmail.com>
Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.12.y | Present (different SHA1: fa1fbb67e081)
Note: The patch differs from the upstream commit:
---
1: 3f23ee5590d96 ! 1: d9b5cb443bdde selftests/bpf: test for changing packet data from global functions
@@ Metadata
## Commit message ##
selftests/bpf: test for changing packet data from global functions
+ commit 3f23ee5590d9605dbde9a5e1d4b97637a4803329 upstream.
+
Check if verifier is aware of packet pointers invalidation done in
global functions. Based on a test shared by Nick Zavaritsky in [0].
@@ Commit message
Signed-off-by: Eduard Zingerman <eddyz87@gmail.com>
Link: https://lore.kernel.org/r/20241210041100.1898468-5-eddyz87@gmail.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
+ Signed-off-by: Shung-Hsi Yu <shung-hsi.yu@suse.com>
## tools/testing/selftests/bpf/progs/verifier_sock.c ##
-@@ tools/testing/selftests/bpf/progs/verifier_sock.c: __naked void sock_create_read_src_port(void)
+@@ tools/testing/selftests/bpf/progs/verifier_sock.c: l1_%=: r0 = *(u8*)(r7 + 0); \
: __clobber_all);
}
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Success | Success |
next prev parent reply other threads:[~2025-05-01 19:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 8:19 [PATCH stable 6.6 00/10] bpf: track changes_pkt_data property for global functions Shung-Hsi Yu
2025-04-30 8:19 ` [PATCH stable 6.6 01/10] bpf: add find_containing_subprog() utility function Shung-Hsi Yu
2025-05-01 19:09 ` Sasha Levin
2025-04-30 8:19 ` [PATCH stable 6.6 02/10] bpf: refactor bpf_helper_changes_pkt_data to use helper number Shung-Hsi Yu
2025-05-01 18:51 ` Sasha Levin
2025-04-30 8:19 ` [PATCH stable 6.6 03/10] bpf: track changes_pkt_data property for global functions Shung-Hsi Yu
2025-05-01 18:51 ` Sasha Levin
2025-04-30 8:19 ` [PATCH stable 6.6 04/10] selftests/bpf: test for changing packet data from " Shung-Hsi Yu
2025-05-01 19:11 ` Sasha Levin [this message]
2025-04-30 8:19 ` [PATCH stable 6.6 05/10] bpf: check changes_pkt_data property for extension programs Shung-Hsi Yu
2025-05-01 18:50 ` Sasha Levin
2025-04-30 8:19 ` [PATCH stable 6.6 06/10] selftests/bpf: freplace tests for tracking of changes_packet_data Shung-Hsi Yu
2025-05-01 18:51 ` Sasha Levin
2025-04-30 8:19 ` [PATCH stable 6.6 07/10] bpf: consider that tail calls invalidate packet pointers Shung-Hsi Yu
2025-05-01 19:10 ` Sasha Levin
2025-04-30 8:19 ` [PATCH stable 6.6 08/10] selftests/bpf: validate that tail call invalidates " Shung-Hsi Yu
2025-05-01 19:10 ` Sasha Levin
2025-04-30 8:19 ` [PATCH stable 6.6 09/10] bpf: fix null dereference when computing changes_pkt_data of prog w/o subprogs Shung-Hsi Yu
2025-05-01 18:52 ` Sasha Levin
2025-04-30 8:19 ` [PATCH stable 6.6 10/10] selftests/bpf: extend changes_pkt_data with cases w/o subprograms Shung-Hsi Yu
2025-05-01 19:10 ` 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=20250501085413-c3dc132b416533b6@stable.kernel.org \
--to=sashal@kernel.org \
--cc=shung-hsi.yu@suse.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 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.