[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1738e24239cc0c001245fdd4bd3811175c573ce2.camel@intel.com>
Date: Tue, 12 Aug 2025 18:03:11 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "glaubitz@...sik.fu-berlin.de" <glaubitz@...sik.fu-berlin.de>,
"peterz@...radead.org" <peterz@...radead.org>, "mingo@...hat.com"
<mingo@...hat.com>, "luto@...nel.org" <luto@...nel.org>, "namit@...are.com"
<namit@...are.com>, "bp@...en8.de" <bp@...en8.de>
CC: "ard.biesheuvel@...aro.org" <ard.biesheuvel@...aro.org>, "sam@...too.org"
<sam@...too.org>, "andreas@...sler.com" <andreas@...sler.com>,
"nadav.amit@...il.com" <nadav.amit@...il.com>, "dave.hansen@...ux.intel.com"
<dave.hansen@...ux.intel.com>, "anthony.yznaga@...cle.com"
<anthony.yznaga@...cle.com>, "akpm@...ux-foundation.org"
<akpm@...ux-foundation.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "will.deacon@....com" <will.deacon@....com>,
"linux_dti@...oud.com" <linux_dti@...oud.com>, "deneen.t.dock@...el.com"
<deneen.t.dock@...el.com>, "linux-mm@...ck.org" <linux-mm@...ck.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"linux-security-module@...r.kernel.org"
<linux-security-module@...r.kernel.org>, "sparclinux@...r.kernel.org"
<sparclinux@...r.kernel.org>, "hpa@...or.com" <hpa@...or.com>,
"linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>,
"daniel@...earbox.net" <daniel@...earbox.net>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>,
"ast@...nel.org" <ast@...nel.org>, "x86@...nel.org" <x86@...nel.org>,
"kristen@...ux.intel.com" <kristen@...ux.intel.com>
Subject: Re: [PATCH v5 18/23] bpf: Use vmalloc special flag
On Tue, 2025-08-12 at 18:43 +0200, John Paul Adrian Glaubitz wrote:
> I suspect that the main issue is to be found in the following patch which introduced VM_FLUSH_RESET_PERMS
> which may not work as expected on sun4u SPARC systems:
I think the problem we found with VM_FLUSH_RESET_PERMS was that the sparc64
kernel TLB flush implementation was broken. Since VM_FLUSH_RESET_PERMS caused
kernel TLB flushes to happen sooner, it just showed up sooner. [0]
This other issue seems to be about userspace memory. So I wonder if these are
two separate issues? Bisecting to the original VM_FLUSH_RESET_PERMS would have
had the known sparc kernel range TLB flush issue. So to bisect the other issue
you might need to apply this [1].
[0] https://marc.info/?l=linux-sparc&m=155915694304118&w=2
[1] https://lore.kernel.org/all/57385AAB-C9A1-46AD-B743-445D4ECCA902@jrtc27.com/
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
