From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>,
"peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"luto@kernel.org" <luto@kernel.org>,
"namit@vmware.com" <namit@vmware.com>,
"bp@alien8.de" <bp@alien8.de>
Cc: "ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
"sam@gentoo.org" <sam@gentoo.org>,
"andreas@gaisler.com" <andreas@gaisler.com>,
"nadav.amit@gmail.com" <nadav.amit@gmail.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"anthony.yznaga@oracle.com" <anthony.yznaga@oracle.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"linux_dti@icloud.com" <linux_dti@icloud.com>,
"deneen.t.dock@intel.com" <deneen.t.dock@intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
"ast@kernel.org" <ast@kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"kristen@linux.intel.com" <kristen@linux.intel.com>
Subject: Re: [PATCH v5 18/23] bpf: Use vmalloc special flag
Date: Tue, 12 Aug 2025 18:03:11 +0000 [thread overview]
Message-ID: <1738e24239cc0c001245fdd4bd3811175c573ce2.camel@intel.com> (raw)
In-Reply-To: <14437e403ed8fceacafe0a89521d3b731211156e.camel@physik.fu-berlin.de>
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/
next prev parent reply other threads:[~2025-08-12 18:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 0:11 [PATCH v5 00/23] x86: text_poke() fixes and executable lockdowns Nadav Amit
2019-04-26 0:11 ` [PATCH v5 01/23] Fix "x86/alternatives: Lockdep-enforce text_mutex in text_poke*()" Nadav Amit
2019-04-26 0:11 ` [PATCH v5 02/23] x86/jump_label: Use text_poke_early() during early init Nadav Amit
2019-04-26 0:11 ` [PATCH v5 03/23] x86/mm: Introduce temporary mm structs Nadav Amit
2019-04-26 0:11 ` [PATCH v5 04/23] x86/mm: Save debug registers when loading a temporary mm Nadav Amit
2019-04-26 0:11 ` [PATCH v5 05/23] fork: Provide a function for copying init_mm Nadav Amit
2019-04-26 0:11 ` [PATCH v5 06/23] x86/alternative: Initialize temporary mm for patching Nadav Amit
2019-04-26 0:11 ` [PATCH v5 07/23] x86/alternative: Use temporary mm for text poking Nadav Amit
2019-04-26 0:11 ` [PATCH v5 08/23] x86/kgdb: Avoid redundant comparison of patched code Nadav Amit
2019-04-26 0:11 ` [PATCH v5 09/23] x86/ftrace: Set trampoline pages as executable Nadav Amit
2019-04-26 0:11 ` [PATCH v5 10/23] x86/kprobes: Set instruction page " Nadav Amit
2019-04-26 0:11 ` [PATCH v5 11/23] x86/module: Avoid breaking W^X while loading modules Nadav Amit
2019-04-26 0:11 ` [PATCH v5 12/23] x86/jump-label: Remove support for custom poker Nadav Amit
2019-04-26 0:11 ` [PATCH v5 13/23] x86/alternative: Remove the return value of text_poke_*() Nadav Amit
2019-04-26 0:11 ` [PATCH v5 14/23] x86/mm/cpa: Add set_direct_map_ functions Nadav Amit
2019-04-26 16:40 ` Linus Torvalds
2019-04-26 16:43 ` Nadav Amit
2019-04-26 0:11 ` [PATCH v5 15/23] mm: Make hibernate handle unmapped pages Nadav Amit
2019-04-26 0:11 ` [PATCH v5 16/23] vmalloc: Add flag for free of special permsissions Nadav Amit
2019-04-26 0:11 ` [PATCH v5 17/23] modules: Use vmalloc special flag Nadav Amit
2019-04-26 0:11 ` [PATCH v5 18/23] bpf: " Nadav Amit
2025-08-12 16:43 ` John Paul Adrian Glaubitz
2025-08-12 18:03 ` Edgecombe, Rick P [this message]
2025-08-12 18:37 ` John Paul Adrian Glaubitz
2025-08-12 18:49 ` Edgecombe, Rick P
2025-08-12 18:59 ` John Paul Adrian Glaubitz
2019-04-26 0:11 ` [PATCH v5 19/23] x86/ftrace: " Nadav Amit
2019-04-26 0:11 ` [PATCH v5 20/23] x86/kprobes: " Nadav Amit
2019-04-26 0:11 ` [PATCH v5 21/23] x86/alternative: Comment about module removal races Nadav Amit
2019-04-26 0:11 ` [PATCH v5 22/23] mm/tlb: Provide default nmi_uaccess_okay() Nadav Amit
2019-04-26 0:11 ` [PATCH v5 23/23] bpf: Fail bpf_probe_write_user() while mm is switched Nadav Amit
2019-04-26 12:36 ` [PATCH v5 00/23] x86: text_poke() fixes and executable lockdowns Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1738e24239cc0c001245fdd4bd3811175c573ce2.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andreas@gaisler.com \
--cc=anthony.yznaga@oracle.com \
--cc=ard.biesheuvel@linaro.org \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=deneen.t.dock@intel.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hpa@zytor.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=kristen@linux.intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux_dti@icloud.com \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=nadav.amit@gmail.com \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=sam@gentoo.org \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox