From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, shung-hsi.yu@suse.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH stable 6.12 4/8] bpf: check changes_pkt_data property for extension programs
Date: Wed, 23 Apr 2025 08:16:55 -0400 [thread overview]
Message-ID: <20250423080247-4a3b6a2dd1fa3c82@stable.kernel.org> (raw)
In-Reply-To: <20250423055334.52791-5-shung-hsi.yu@suse.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
ℹ️ This is part 4/8 of a series
⚠️ Found follow-up fixes in mainline
The upstream commit SHA1 provided is correct: 81f6d0530ba031b5f038a091619bf2ff29568852
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)
Found fixes commits:
ac6542ad9275 bpf: fix null dereference when computing changes_pkt_data of prog w/o subprogs
Note: The patch differs from the upstream commit:
---
1: 81f6d0530ba03 ! 1: 55bebf976e68c bpf: check changes_pkt_data property for extension programs
@@ Metadata
## Commit message ##
bpf: check changes_pkt_data property for extension programs
+ commit 81f6d0530ba031b5f038a091619bf2ff29568852 upstream.
+
When processing calls to global sub-programs, verifier decides whether
to invalidate all packet pointers in current state depending on the
changes_pkt_data property of the global sub-program.
@@ Commit message
Signed-off-by: Eduard Zingerman <eddyz87@gmail.com>
Link: https://lore.kernel.org/r/20241210041100.1898468-6-eddyz87@gmail.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
+ [ shung-hsi.yu: both jits_use_priv_stack and priv_stack_requested fields are
+ missing from context because "bpf: Support private stack for bpf progs" series
+ is not present.]
+ Signed-off-by: Shung-Hsi Yu <shung-hsi.yu@suse.com>
## include/linux/bpf.h ##
@@ include/linux/bpf.h: struct bpf_prog_aux {
+ bool exception_cb;
+ bool exception_boundary;
bool is_extended; /* true if extended by freplace program */
- bool jits_use_priv_stack;
- bool priv_stack_requested;
+ bool changes_pkt_data;
u64 prog_array_member_cnt; /* counts how many times as member of prog_array */
struct mutex ext_mutex; /* mutex for is_extended and prog_array_member_cnt */
---
NOTE: These results are for this patch alone. Full series testing will be
performed when all parts are received.
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.14.y | Success | Success |
next prev parent reply other threads:[~2025-04-23 12:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 5:53 [PATCH stable 6.12 0/8] bpf: track changes_pkt_data property for global functions Shung-Hsi Yu
2025-04-23 5:53 ` [PATCH stable 6.12 1/8] bpf: add find_containing_subprog() utility function Shung-Hsi Yu
2025-04-23 12:17 ` Sasha Levin
2025-04-23 5:53 ` [PATCH stable 6.12 2/8] bpf: track changes_pkt_data property for global functions Shung-Hsi Yu
2025-04-23 12:17 ` Sasha Levin
2025-04-23 5:53 ` [PATCH stable 6.12 3/8] selftests/bpf: test for changing packet data from " Shung-Hsi Yu
2025-04-23 12:16 ` Sasha Levin
2025-04-23 5:53 ` [PATCH stable 6.12 4/8] bpf: check changes_pkt_data property for extension programs Shung-Hsi Yu
2025-04-23 12:16 ` Sasha Levin [this message]
2025-04-23 5:53 ` [PATCH stable 6.12 5/8] selftests/bpf: freplace tests for tracking of changes_packet_data Shung-Hsi Yu
2025-04-23 12:16 ` Sasha Levin
2025-04-23 5:53 ` [PATCH stable 6.12 6/8] selftests/bpf: validate that tail call invalidates packet pointers Shung-Hsi Yu
2025-04-23 12:16 ` Sasha Levin
2025-04-23 5:53 ` [PATCH stable 6.12 7/8] bpf: fix null dereference when computing changes_pkt_data of prog w/o subprogs Shung-Hsi Yu
2025-04-23 12:17 ` Sasha Levin
2025-04-23 5:53 ` [PATCH stable 6.12 8/8] selftests/bpf: extend changes_pkt_data with cases w/o subprograms Shung-Hsi Yu
2025-04-23 12:16 ` 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=20250423080247-4a3b6a2dd1fa3c82@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.