[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <afd8091d11429e63949a16fc24228078b08c7726.camel@gmail.com>
Date: Wed, 27 Aug 2025 00:01:09 -0700
From: Eduard Zingerman <eddyz87@...il.com>
To: Andrea Righi <arighi@...dia.com>
Cc: Yonghong Song <yonghong.song@...ux.dev>, Alexei Starovoitov
<ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>, Andrii Nakryiko
<andrii@...nel.org>, Martin KaFai Lau <martin.lau@...ux.dev>, Song Liu
<song@...nel.org>, 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>, David Vernet
<void@...ifault.com>, bpf@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] bpf: Mark kfuncs as __noclone
On Tue, 2025-08-26 at 23:52 -0700, Eduard Zingerman wrote:
[...]
> If we are being really paranoid about LTO builds, is __noclone sufficient?
> E.g. [1] does not imply that signature can't be changed.
> We currently apply only __retain__, here is a little test with both attributes:
Nope, there are also 'used' and 'noinline' applied.
With these the function is preserved as expected.
Sorry for the noise.
[...]
Powered by blists - more mailing lists