From: Eduard Zingerman <eddyz87@gmail.com>
To: Sergei Trofimovich <slyich@gmail.com>, bpf@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH] tools/lib/bpf: add pr_warn() to more -EINVAL cases
Date: Fri, 08 Dec 2023 00:58:02 +0200 [thread overview]
Message-ID: <159e94e7ce82e9432bd2bba0141c8feab0a9a2e6.camel@gmail.com> (raw)
In-Reply-To: <20231207180919.2379718-1-slyich@gmail.com>
On Thu, 2023-12-07 at 18:09 +0000, Sergei Trofimovich wrote:
> Before the change on `i686-linux` `systemd` build failed as:
>
> $ bpftool gen object src/core/bpf/socket_bind/socket-bind.bpf.o src/core/bpf/socket_bind/socket-bind.bpf.unstripped.o
> Error: failed to link 'src/core/bpf/socket_bind/socket-bind.bpf.unstripped.o': Invalid argument (22)
>
> After the change it fails as:
>
> $ bpftool gen object src/core/bpf/socket_bind/socket-bind.bpf.o src/core/bpf/socket_bind/socket-bind.bpf.unstripped.o
> libbpf: ELF section #9 has inconsistent alignment in src/core/bpf/socket_bind/socket-bind.bpf.unstripped.o
> Error: failed to link 'src/core/bpf/socket_bind/socket-bind.bpf.unstripped.o': Invalid argument (22)
>
> Now it's slightly easier to figure out what is wrong with an ELF file.
Hi Sergei,
Thank you for adding these prints.
Could you please make a few adjustments, as noted below.
Also, please add "libbpf:" prefix in subject and mention
linker_sanity_check_elf in it, e.g.:
libbpf: add pr_warn() for EINVAL cases in linker_sanity_check_elf
or something like that.
[...]
> diff --git a/tools/lib/bpf/linker.c b/tools/lib/bpf/linker.c
> index 5ced96d99f8c..71bb4916b762 100644
> --- a/tools/lib/bpf/linker.c
> +++ b/tools/lib/bpf/linker.c
> @@ -719,13 +719,22 @@ static int linker_sanity_check_elf(struct src_obj *obj)
> return -EINVAL;
> }
>
> - if (sec->shdr->sh_addralign && !is_pow_of_2(sec->shdr->sh_addralign))
> + if (sec->shdr->sh_addralign && !is_pow_of_2(sec->shdr->sh_addralign)) {
> + pr_warn("ELF section #%zu alignment is non pow-of-2 alignment in %s\n",
> + sec->sec_idx, obj->filename);
Could you please also print values for shdr->sh_addralign here?
And also print shdr->sh_addralign/data->d_align, shdr->sh_size/data->d_size
in corresponding pr_warn() calls below.
> return -EINVAL;
> - if (sec->shdr->sh_addralign != sec->data->d_align)
> + }
> + if (sec->shdr->sh_addralign != sec->data->d_align) {
> + pr_warn("ELF section #%zu has inconsistent alignment in %s\n",
> + sec->sec_idx, obj->filename);
> return -EINVAL;
> + }
>
> - if (sec->shdr->sh_size != sec->data->d_size)
> + if (sec->shdr->sh_size != sec->data->d_size) {
> + pr_warn("ELF section #%zu has inconsistent section size in %s\n",
> + sec->sec_idx, obj->filename);
> return -EINVAL;
> + }
>
> switch (sec->shdr->sh_type) {
> case SHT_SYMTAB:
A few lines below this one there is:
case SHT_PROGBITS:
if (sec->shdr->sh_flags & SHF_EXECINSTR) {
if (sec->shdr->sh_size % sizeof(struct bpf_insn) != 0)
return -EINVAL;
}
break;
Could you please add pr_warn() there as well?
next prev parent reply other threads:[~2023-12-07 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 18:09 [PATCH] tools/lib/bpf: add pr_warn() to more -EINVAL cases Sergei Trofimovich
2023-12-07 22:58 ` Eduard Zingerman [this message]
2023-12-08 21:51 ` [PATCH v2] libbpf: add pr_warn() for EINVAL cases in linker_sanity_check_elf Sergei Trofimovich
2023-12-08 22:00 ` Eduard Zingerman
2023-12-09 1: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=159e94e7ce82e9432bd2bba0141c8feab0a9a2e6.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=slyich@gmail.com \
--cc=song@kernel.org \
--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