public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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.12 2/8] bpf: track changes_pkt_data property for global functions
Date: Wed, 23 Apr 2025 08:17:15 -0400	[thread overview]
Message-ID: <20250423074616-bfadb6b016e3d6c4@stable.kernel.org> (raw)
In-Reply-To: <20250423055334.52791-3-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: 51081a3f25c742da5a659d7fc6fd77ebfdd555be

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)

Note: The patch differs from the upstream commit:
---
1:  51081a3f25c74 ! 1:  6678a7d80c020 bpf: track changes_pkt_data property for global functions
    @@ Metadata
      ## Commit message ##
         bpf: track changes_pkt_data property for global functions
     
    +    commit 51081a3f25c742da5a659d7fc6fd77ebfdd555be upstream.
    +
         When processing calls to certain helpers, verifier invalidates all
         packet pointers in a current state. For example, consider the
         following program:
    @@ Commit message
         Signed-off-by: Eduard Zingerman <eddyz87@gmail.com>
         Link: https://lore.kernel.org/r/20241210041100.1898468-4-eddyz87@gmail.com
         Signed-off-by: Alexei Starovoitov <ast@kernel.org>
    +    Signed-off-by: Shung-Hsi Yu <shung-hsi.yu@suse.com>
     
      ## include/linux/bpf_verifier.h ##
     @@ include/linux/bpf_verifier.h: struct bpf_subprog_info {
    @@ include/linux/bpf_verifier.h: struct bpf_subprog_info {
      	bool keep_fastcall_stack: 1;
     +	bool changes_pkt_data: 1;
      
    - 	enum priv_stack_mode priv_stack_mode;
      	u8 arg_cnt;
    + 	struct bpf_subprog_arg_info args[MAX_BPF_FUNC_REG_ARGS];
     
      ## kernel/bpf/verifier.c ##
     @@ kernel/bpf/verifier.c: static int check_func_call(struct bpf_verifier_env *env, struct bpf_insn *insn,
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.14.y       |  Success    |  Success   |

  reply	other threads:[~2025-04-23 12:17 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 [this message]
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
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=20250423074616-bfadb6b016e3d6c4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox