From: Blaise Boscaccy <bboscaccy@linux.microsoft.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf@vger.kernel.org, nkapron@google.com, teknoraver@meta.com,
roberto.sassu@huawei.com, paul@paul-moore.com, code@tyhicks.com,
xiyou.wangcong@gmail.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org
Subject: Re: [PATCH 1/1] libbpf: Convert ELF notes into read-only maps
Date: Thu, 06 Feb 2025 10:34:08 -0800 [thread overview]
Message-ID: <874j169b33.fsf@microsoft.com> (raw)
In-Reply-To: <CAEf4BzZQUPfA8UcW1Ed9jM0J8z+yGHe=kOM5BwEBuDzJL3B1HA@mail.gmail.com>
Andrii Nakryiko <andrii.nakryiko@gmail.com> writes:
> On Wed, Feb 5, 2025 at 11:09 AM Blaise Boscaccy
> <bboscaccy@linux.microsoft.com> wrote:
>>
>> Add a flexible mechanism, using existing ELF constructs, to attach
>> additional metadata to BPF programs for possible use by BPF
>> gatekeepers and skeletons.
>>
>> During object file parsing, note sections are no longer skipped and
>> now treated as read-only data. During libbpf-based loading or skeleton
>> generation, those sections are then transformed into read-only maps
>> which are subsequently passed into the kernel.
>
> We already have this mechanism, it's .rodata (and
> .rodata.<customname>) section(s). Adding .note sections as BPF maps
> make no sense to me. Just piggy-back on .rodata for storing any
> necessary metadata.
>
> pw-bot: cr
>
The ELF specification clearly states:
"Sometimes a vendor or system builder needs to mark an object file with
special information that other programs will check for conformance,
compatibility, etc. Sections of type SHT_NOTE and program header
elements of type PT_NOTE can be used for this purpose."
Which is exactly what we are trying to do. They make no mention of
piggy-backing off of .rodata.
Further, one can generally strip away .note sections and be left with an
object that's still functioning. The same cannot be said about .rodata.
>>
>> Signed-off-by: Blaise Boscaccy <bboscaccy@linux.microsoft.com>
>> ---
>> tools/bpf/bpftool/gen.c | 4 ++--
>> tools/lib/bpf/libbpf.c | 6 ++++++
>> 2 files changed, 8 insertions(+), 2 deletions(-)
>>
>> diff --git a/tools/bpf/bpftool/gen.c b/tools/bpf/bpftool/gen.c
>> index 5a4d3240689ed..311d6a3f1c4bb 100644
>> --- a/tools/bpf/bpftool/gen.c
>> +++ b/tools/bpf/bpftool/gen.c
>> @@ -92,7 +92,7 @@ static void get_header_guard(char *guard, const char *obj_name, const char *suff
>>
>> static bool get_map_ident(const struct bpf_map *map, char *buf, size_t buf_sz)
>> {
>> - static const char *sfxs[] = { ".data", ".rodata", ".bss", ".kconfig" };
>> + static const char *sfxs[] = { ".data", ".rodata", ".bss", ".kconfig", ".note" };
>> const char *name = bpf_map__name(map);
>> int i, n;
>>
>> @@ -117,7 +117,7 @@ static bool get_map_ident(const struct bpf_map *map, char *buf, size_t buf_sz)
>>
>> static bool get_datasec_ident(const char *sec_name, char *buf, size_t buf_sz)
>> {
>> - static const char *pfxs[] = { ".data", ".rodata", ".bss", ".kconfig" };
>> + static const char *pfxs[] = { ".data", ".rodata", ".bss", ".kconfig", ".note" };
>> int i, n;
>>
>> /* recognize hard coded LLVM section name */
>> diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
>> index 194809da51725..be6af0fece040 100644
>> --- a/tools/lib/bpf/libbpf.c
>> +++ b/tools/lib/bpf/libbpf.c
>> @@ -523,6 +523,7 @@ struct bpf_struct_ops {
>> #define STRUCT_OPS_SEC ".struct_ops"
>> #define STRUCT_OPS_LINK_SEC ".struct_ops.link"
>> #define ARENA_SEC ".addr_space.1"
>> +#define NOTE_SEC ".note"
>>
>> enum libbpf_map_type {
>> LIBBPF_MAP_UNSPEC,
>> @@ -3977,6 +3978,11 @@ static int bpf_object__elf_collect(struct bpf_object *obj)
>> sec_desc->sec_type = SEC_BSS;
>> sec_desc->shdr = sh;
>> sec_desc->data = data;
>> + } else if (sh->sh_type == SHT_NOTE && (strcmp(name, NOTE_SEC) == 0 ||
>> + str_has_pfx(name, NOTE_SEC "."))) {
>> + sec_desc->sec_type = SEC_RODATA;
>> + sec_desc->shdr = sh;
>> + sec_desc->data = data;
>> } else {
>> pr_info("elf: skipping section(%d) %s (size %zu)\n", idx, name,
>> (size_t)sh->sh_size);
>> --
>> 2.48.1
>>
next prev parent reply other threads:[~2025-02-06 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 19:06 [PATCH 0/1] libbpf: Convert ELF notes into read-only maps Blaise Boscaccy
2025-02-05 19:06 ` [PATCH 1/1] " Blaise Boscaccy
2025-02-05 21:22 ` Andrii Nakryiko
2025-02-06 18:34 ` Blaise Boscaccy [this message]
2025-02-06 22:04 ` Andrii Nakryiko
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=874j169b33.fsf@microsoft.com \
--to=bboscaccy@linux.microsoft.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=code@tyhicks.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=nkapron@google.com \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=teknoraver@meta.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yonghong.song@linux.dev \
/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