From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Shung-Hsi Yu <shung-hsi.yu@suse.com>
Cc: stable@vger.kernel.org, Eduard Zingerman <eddyz87@gmail.com>,
ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, yhs@fb.com, mykolal@fb.com,
luizcap@amazon.com
Subject: Re: [PATCH 6.1.y v2 1/6] bpf: allow precision tracking for programs with subprogs
Date: Tue, 2 Jul 2024 10:48:07 +0200 [thread overview]
Message-ID: <2024070249-cannabis-shakily-842b@gregkh> (raw)
In-Reply-To: <tof56dmde2ykrnqy33pz7evpzlwskpxnmxf3wa4lkeinhjung6@zthg6lsnmnwf>
On Tue, Jun 25, 2024 at 03:28:31PM +0800, Shung-Hsi Yu wrote:
> Hi Greg,
>
> On Mon, Jul 24, 2023 at 03:42:18PM GMT, Eduard Zingerman wrote:
> > [ Upstream commit be2ef8161572ec1973124ebc50f56dafc2925e07 ]
> >
> ...
> > --- a/kernel/bpf/verifier.c
> > +++ b/kernel/bpf/verifier.c
> ...
> > @@ -2670,6 +2679,11 @@ static int backtrack_insn(struct bpf_verifier_env *env, int idx,
> > */
> > if (insn->src_reg == BPF_PSEUDO_KFUNC_CALL && insn->imm == 0)
> > return -ENOTSUPP;
> > + /* BPF helpers that invoke callback subprogs are
> > + * equivalent to BPF_PSEUDO_CALL above
> > + */
> > + if (insn->src_reg == 0 && is_callback_calling_function(insn->imm))
> > + return -ENOTSUPP;
> > /* regular helper call sets R0 */
> > *reg_mask &= ~1;
> > if (*reg_mask & 0x3f) {
>
> Looks like the above hunk is slightly misplaced.
>
> In master the lines are added _before_ the BPF_PSEUDO_KFUNC_CALL check,
> resulting in deviation from upstream as well as interfering with
> backporting of commit be2ef8161572 ("bpf: allow precision tracking for
> programs with subprogs") to stable v6.1.
>
> What would be the suggested action here?
> 1. Send a updated version of the whole be2ef8161572 patch to stable
> 2. Send a minimal refresh patch like the one found in this email to
> stable
> 3. Adapt to this deviation in my backport of commit be2ef8161572 for
> stable
Please send a fix-up patch for this as I can't change the existing
releases.
thanks,
greg k-h
next prev parent reply other threads:[~2024-07-02 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 12:42 [PATCH 6.1.y v2 0/6] BPF selftests fixes for 6.1 branch Eduard Zingerman
2023-07-24 12:42 ` [PATCH 6.1.y v2 1/6] bpf: allow precision tracking for programs with subprogs Eduard Zingerman
2024-06-25 7:28 ` Shung-Hsi Yu
2024-07-02 8:48 ` Greg Kroah-Hartman [this message]
2023-07-24 12:42 ` [PATCH 6.1.y v2 2/6] bpf: stop setting precise in current state Eduard Zingerman
2023-07-24 12:42 ` [PATCH 6.1.y v2 3/6] bpf: aggressively forget precise markings during state checkpointing Eduard Zingerman
2023-07-24 12:42 ` [PATCH 6.1.y v2 4/6] selftests/bpf: make test_align selftest more robust Eduard Zingerman
2023-07-24 12:42 ` [PATCH 6.1.y v2 5/6] selftests/bpf: Workaround verification failure for fexit_bpf2bpf/func_replace_return_code Eduard Zingerman
2023-07-24 12:42 ` [PATCH 6.1.y v2 6/6] selftests/bpf: Fix sk_assign on s390x Eduard Zingerman
2023-07-25 10:22 ` [PATCH 6.1.y v2 0/6] BPF selftests fixes for 6.1 branch Greg KH
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=2024070249-cannabis-shakily-842b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=luizcap@amazon.com \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=shung-hsi.yu@suse.com \
--cc=stable@vger.kernel.org \
--cc=yhs@fb.com \
/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