[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024070815-udder-charging-7f75@gregkh>
Date: Mon, 8 Jul 2024 14:36:39 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: WangYuli <wangyuli@...ontech.com>
Cc: stable@...r.kernel.org, sashal@...nel.org, ast@...nel.org,
keescook@...omium.org, linux-hardening@...r.kernel.org,
christophe.leroy@...roup.eu, catalin.marinas@....com,
song@...nel.org, puranjay12@...il.com, daniel@...earbox.net,
andrii@...nel.org, martin.lau@...ux.dev, yonghong.song@...ux.dev,
john.fastabend@...il.com, kpsingh@...nel.org, sdf@...gle.com,
haoluo@...gle.com, jolsa@...nel.org, illusionist.neo@...il.com,
linux@...linux.org.uk, bpf@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
chenhuacai@...nel.org, kernel@...0n.name, loongarch@...ts.linux.dev,
johan.almbladh@...finetworks.com, paulburton@...nel.org,
tsbogend@...ha.franken.de, linux-mips@...r.kernel.org,
deller@....de, linux-parisc@...r.kernel.org, iii@...ux.ibm.com,
hca@...ux.ibm.com, gor@...ux.ibm.com, agordeev@...ux.ibm.com,
borntraeger@...ux.ibm.com, svens@...ux.ibm.com,
linux-s390@...r.kernel.org, davem@...emloft.net,
sparclinux@...r.kernel.org, kuba@...nel.org, hawk@...nel.org,
netdev@...r.kernel.org, dsahern@...nel.org, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com,
x86@...nel.org, hpa@...or.com, guanwentao@...ontech.com,
baimingcong@...ontech.com
Subject: Re: [PATCH] Revert "bpf: Take return from set_memory_rox() into
account with bpf_jit_binary_lock_ro()" for linux-6.6.37
On Sun, Jul 07, 2024 at 03:34:15PM +0800, WangYuli wrote:
>
> On 2024/7/6 17:30, Greg KH wrote:
> > This makes it sound like you are reverting this because of a build
> > error, which is not the case here, right? Isn't this because of the
> > powerpc issue reported here:
> > https://lore.kernel.org/r/20240705203413.wbv2nw3747vjeibk@altlinux.org
> > ?
>
> No, it only occurs on ARM64 architecture. The reason is that before being
> modified, the function
>
> bpf_jit_binary_lock_ro() in arch/arm64/net/bpf_jit_comp.c +1651
>
> was introduced with __must_check, which is defined as
> __attribute__((__warn_unused_result__)).
>
>
> However, at this point, calling bpf_jit_binary_lock_ro(header)
> coincidentally results in an unused-result
>
> warning.
Ok, thanks, but why is no one else seeing this in their testing?
> > If not, why not just backport the single missing arm64 commit,
>
> Upstream commit 1dad391daef1 ("bpf, arm64: use bpf_prog_pack for memory
> management") is part of
>
> a larger change that involves multiple commits. It's not an isolated commit.
>
>
> We could certainly backport all of them to solve this problem, but it's not
> the simplest solution.
reverting the change feels wrong in that you will still have the bug
present that it was trying to solve, right? If so, can you then provide
a working version?
thanks,
greg k-h
Powered by blists - more mailing lists