From: Martin KaFai Lau <martin.lau@linux.dev>
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@meta.com, Robert Morris <rtm@csail.mit.edu>
Subject: Re: [PATCH bpf-next] bpf: Reject struct_ops registration that uses module ptr and the module btf_id is missing
Date: Mon, 6 Jan 2025 16:34:46 -0800 [thread overview]
Message-ID: <932975bf-e413-4eb6-9643-5102f68b1905@linux.dev> (raw)
In-Reply-To: <1983b3bd389865ddf33d80e9a990c6749eae29b9.camel@gmail.com>
On 1/2/25 10:14 PM, Eduard Zingerman wrote:
> It was a bit hard for me to figure out what went wrong from the description,
> could you please double-check my understanding below?
> - when struct_ops program is attached,
> bpf_struct_ops_map_update_elem() scans every member of specific
> struct_ops type (e.g. struct tcp_congestion_ops) looking for fields
> with type 'struct module *';
> - to find these fields BTF id of 'struct module' is used, this id does
> not exist when CONFIG_MODULES=n, bpf_struct_ops_map_update_elem()
> does not check if 'struct module' BTF id is non-zero;
> - bpf_struct_ops_map_update_elem() initializes 'struct module *'
> fields using a magic value BPF_MODULE_OWNER, this initialization
> would not happen if fields are not found;
Thanks for reviewing and testing it!
Yes, the understanding is correct. These are pretty much the only two places
where st_ops_ids[IDX_MODULE_ID] and BPF_MODULE_OWNER are used.
next prev parent reply other threads:[~2025-01-07 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 20:18 [PATCH bpf-next] bpf: Reject struct_ops registration that uses module ptr and the module btf_id is missing Martin KaFai Lau
2025-01-03 6:14 ` Eduard Zingerman
2025-01-07 0:34 ` Martin KaFai Lau [this message]
2025-01-03 18:20 ` patchwork-bot+netdevbpf
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=932975bf-e413-4eb6-9643-5102f68b1905@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@meta.com \
--cc=rtm@csail.mit.edu \
/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