[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e0a51f8c-9d09-4e99-b6f6-6a3b0a3363eb@iogearbox.net>
Date: Mon, 2 Dec 2024 16:34:26 +0100
From: Daniel Borkmann <daniel@...earbox.net>
To: Thomas Weißschuh <linux@...ssschuh.net>
Cc: Masahiro Yamada <masahiroy@...nel.org>,
Nathan Chancellor <nathan@...nel.org>, Nicolas Schier <nicolas@...sle.eu>,
Alexei Starovoitov <ast@...nel.org>, Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <martin.lau@...ux.dev>, Eduard Zingerman
<eddyz87@...il.com>, Song Liu <song@...nel.org>,
Yonghong Song <yonghong.song@...ux.dev>,
John Fastabend <john.fastabend@...il.com>, KP Singh <kpsingh@...nel.org>,
Stanislav Fomichev <sdf@...ichev.me>, Hao Luo <haoluo@...gle.com>,
Jiri Olsa <jolsa@...nel.org>, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: [PATCH v2 0/2] kbuild: propagate CONFIG_WERROR to resolve_btfids
On 12/2/24 4:32 PM, Thomas Weißschuh wrote:
> On 2024-12-02 16:28:07+0100, Daniel Borkmann wrote:
>> On 11/26/24 10:17 PM, Thomas Weißschuh wrote:
>>> Use CONFIG_WERROR to also fail on warnings emitted by resolve_btfids.
>>> Allow the CI bots to prevent the introduction of new warnings.
>>>
>>> This series currently depends on
>>> "[PATCH] bpf, lsm: Fix getlsmprop hooks BTF IDs" [0]
>>>
>>> [0] https://lore.kernel.org/lkml/20241123-bpf_lsm_task_getsecid_obj-v1-1-0d0f94649e05@weissschuh.net/
>>
>> Given this is a dependency, do you plan to follow up on [1]?
>
>> [1] https://lore.kernel.org/lkml/Z0TRc0A6Q8QUxNAe@google.com/
>
> I did so in [2], which is already part of the BPF tree.
>
> [2] https://lore.kernel.org/lkml/20241125-bpf_lsm_task_getsecid_obj-v2-1-c8395bde84e0@weissschuh.net/
Perfect, nevermind then!
Powered by blists - more mailing lists