[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1345374f-d47c-81da-e7f3-57b9c22a6328@iogearbox.net>
Date: Fri, 4 Feb 2022 16:42:03 +0100
From: Daniel Borkmann <daniel@...earbox.net>
To: Hou Tao <hotforest@...il.com>
Cc: Alexei Starovoitov <ast@...nel.org>,
Martin KaFai Lau <kafai@...com>, Yonghong Song <yhs@...com>,
Andrii Nakryiko <andrii@...nel.org>,
"David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
John Fastabend <john.fastabend@...il.com>,
netdev@...r.kernel.org, bpf@...r.kernel.org, houtao1@...wei.com,
Zi Shen Lim <zlim.lnx@...il.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Ard Biesheuvel <ard.biesheuvel@....com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH bpf-next v3 1/3] bpf, arm64: enable kfunc call
On 1/30/22 10:29 AM, Hou Tao wrote:
> From: Hou Tao <houtao1@...wei.com>
>
> Since commit b2eed9b58811 ("arm64/kernel: kaslr: reduce module
> randomization range to 2 GB"), for arm64 whether KASLR is enabled
> or not, the module is placed within 2GB of the kernel region, so
> s32 in bpf_kfunc_desc is sufficient to represente the offset of
> module function relative to __bpf_call_base. The only thing needed
> is to override bpf_jit_supports_kfunc_call().
>
> Signed-off-by: Hou Tao <houtao1@...wei.com>
Could you rebase patch 2 & 3 and resend as they don't apply to bpf-next
right now. Meanwhile, applied this one, thanks a lot!
Powered by blists - more mailing lists