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 v2] libbpf: add pr_warn() for EINVAL cases in linker_sanity_check_elf
Date: Sat, 09 Dec 2023 00:00:32 +0200 [thread overview]
Message-ID: <acfff73b4a0b6d325f749b580ee593ce8d0187f6.camel@gmail.com> (raw)
In-Reply-To: <20231208215100.435876-1-slyich@gmail.com>
On Fri, 2023-12-08 at 21:51 +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 addr=8 != d=4 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.
>
> CC: Alexei Starovoitov <ast@kernel.org>
> CC: Daniel Borkmann <daniel@iogearbox.net>
> CC: Andrii Nakryiko <andrii@kernel.org>
> CC: Martin KaFai Lau <martin.lau@linux.dev>
> CC: Song Liu <song@kernel.org>
> CC: Yonghong Song <yonghong.song@linux.dev>
> CC: John Fastabend <john.fastabend@gmail.com>
> CC: KP Singh <kpsingh@kernel.org>
> CC: Stanislav Fomichev <sdf@google.com>
> CC: Hao Luo <haoluo@google.com>
> CC: Jiri Olsa <jolsa@kernel.org>
> CC: Eduard Zingerman <eddyz87@gmail.com>
> CC: bpf@vger.kernel.org
> Signed-off-by: Sergei Trofimovich <slyich@gmail.com>
> ---
> tools/lib/bpf/linker.c | 24 ++++++++++++++++++++----
> 1 file changed, 20 insertions(+), 4 deletions(-)
> Change since v1:
> Following Eduard's suggestion added one extra pr_warn() call around
> section alignment and added compared values into warning messages.
Thank you for doing adjustments.
(Note: when I apply this patch locally full CC block is a part of the
commit message, this is usually omitted from commit messages).
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
next prev parent reply other threads:[~2023-12-08 22:00 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
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 [this message]
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=acfff73b4a0b6d325f749b580ee593ce8d0187f6.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