From: Jakub Sitnicki <jakub@cloudflare.com>
To: "Thiébaud Weksteen" <tweek@google.com>
Cc: bpf@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH] bpf: Fix BPF_PROG_ASSOC_STRUCT_OPS last field check
Date: Thu, 18 Jun 2026 11:58:37 +0200 [thread overview]
Message-ID: <871pe4b25u.fsf@cloudflare.com> (raw)
In-Reply-To: <20260618040934.4113938-1-tweek@google.com> ("Thiébaud Weksteen"'s message of "Thu, 18 Jun 2026 14:09:33 +1000")
On Thu, Jun 18, 2026 at 02:09 PM +10, Thiébaud Weksteen wrote:
> When struct prog_assoc_struct_ops was added,
> BPF_PROG_ASSOC_STRUCT_OPS_LAST_FIELD referenced prog_fd instead of the
> actual last field, flags.
>
> Fixes: b5709f6d26d6 ("bpf: Support associating BPF program with struct_ops")
> Signed-off-by: Thiébaud Weksteen <tweek@google.com>
> ---
You need to indicate which tree the patch should go to [1].
bpf tree in this case since this is a fix.
Reviewed-by: Jakub Sitnicki <jakub@cloudflare.com>
[1] https://docs.kernel.org/bpf/bpf_devel_QA.html#q-how-do-i-indicate-which-tree-bpf-vs-bpf-next-my-patch-should-be-applied-to
prev parent reply other threads:[~2026-06-18 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 4:09 [PATCH] bpf: Fix BPF_PROG_ASSOC_STRUCT_OPS last field check Thiébaud Weksteen
2026-06-18 9:58 ` Jakub Sitnicki [this message]
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=871pe4b25u.fsf@cloudflare.com \
--to=jakub@cloudflare.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=tweek@google.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