From: Jiri Olsa <olsajiri@gmail.com>
To: Dmitrii Bundin <dmitrii.bundin.a@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Jiri Olsa <olsajiri@gmail.com>,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
haoluo@google.com, sdf@google.com, kpsingh@kernel.org,
john.fastabend@gmail.com, yonghong.song@linux.dev,
song@kernel.org, eddyz87@gmail.com, andrii@kernel.org,
ast@kernel.org, martin.lau@linux.dev, khazhy@chromium.org,
vmalik@redhat.com, ndesaulniers@google.com,
ncopa@alpinelinux.org, dxu@dxuuu.xyz
Subject: Re: [PATCH] bpf: btf: include linux/types.h for u32
Date: Wed, 17 Apr 2024 09:17:24 +0200 [thread overview]
Message-ID: <Zh93hKfHgsw5wQAw@krava> (raw)
In-Reply-To: <CANXV_XwGhdV7v05Xjjp-g9yW4E0FjA=84M8jZ6bcf7yuooDkig@mail.gmail.com>
On Wed, Apr 17, 2024 at 09:26:03AM +0300, Dmitrii Bundin wrote:
> On Tue, Apr 16, 2024 at 5:47 PM Daniel Borkmann <daniel@iogearbox.net> wrote:
> > Please add the error description as motivation aka "why" into the commit
> > description, otherwise it's not really obvious looking at it at a later
> > point in time why the include was needed.
>
> Doesn't the comment /* for u32 */ following the include explain the
> purpose? I thought the include was actually missing since relying on
> indirect declaration of u32 is relatively fragile.
I think you can add similar descirption as for the already merged tool
change in bpf/master, and also include the Fixes/stable tags
commit 62248b22d01e96a4d669cde0d7005bd51ebf9e76
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Thu Mar 28 11:59:13 2024 +0100
tools/resolve_btfids: fix build with musl libc
Include the header that defines u32.
This fixes build of 6.6.23 and 6.1.83 kernels for Alpine Linux, which
uses musl libc. I assume that GNU libc indirecly pulls in linux/types.h.
Fixes: 9707ac4fe2f5 ("tools/resolve_btfids: Refactor set sorting with types from btf_ids.h")
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=218647
Cc: stable@vger.kernel.org
Signed-off-by: Natanael Copa <ncopa@alpinelinux.org>
Tested-by: Greg Thelen <gthelen@google.com>
Link: https://lore.kernel.org/r/20240328110103.28734-1-ncopa@alpinelinux.org
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
jirka
next prev parent reply other threads:[~2024-04-17 7:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 4:51 [PATCH] bpf: btf: include linux/types.h for u32 Dmitrii Bundin
2024-04-15 12:11 ` Jiri Olsa
2024-04-16 5:15 ` [PATCH bpf-next v2] " Dmitrii Bundin
2024-04-16 7:23 ` Jiri Olsa
2024-04-16 5:27 ` [PATCH] " Dmitrii Bundin
2024-04-16 7:28 ` Jiri Olsa
2024-04-16 14:47 ` Daniel Borkmann
2024-04-17 6:26 ` Dmitrii Bundin
2024-04-17 7:17 ` Jiri Olsa [this message]
2024-04-20 4:24 ` [PATCH bpf-next v3] " Dmitrii Bundin
2024-04-26 15:54 ` Daniel Borkmann
2024-04-29 23:33 ` Andrii Nakryiko
2024-04-29 23:40 ` 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=Zh93hKfHgsw5wQAw@krava \
--to=olsajiri@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dmitrii.bundin.a@gmail.com \
--cc=dxu@dxuuu.xyz \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=khazhy@chromium.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=ncopa@alpinelinux.org \
--cc=ndesaulniers@google.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=vmalik@redhat.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