s...@kernel.org>, Will Deacon <w...@kernel.org>, Masahiro Yamada <masahi...@kernel.org>, Jarkko Sakkinen <jar...@profian.com>, Sami Tolvanen <samitolva...@google.com>, "Naveen N. Rao" <naveen.n....@linux.ibm.com>, Marco Elver <el...@google.com>, Kees Cook <keesc...@chromium.org>, Steven Rostedt <rost...@goodmis.org>, Nathan Chancellor <nat...@kernel.org>, "Russell King \(Oracle\)" <rmk+ker...@armlinux.org.uk>, Mark Brown <broo...@kernel.org>, Borislav Petkov <b...@alien8.de>, Alexander Egorenkov <egore...@linux.ibm.com>, Thomas Bogendoerfer <tsbog...@alpha.franken.de>, Parisc List <linux-par...@vger.kernel.org>, Nathaniel McCallum <nathan...@profian.com>, Dmitry Torokhov <dmitry.torok...@gmail.com>, "David S. Miller" <da...@davemloft.net>, "Kirill A. Shutemov" <kirill.shute...@linux.intel.com>, Tobias Huschle <husc...@linux.ibm.com>, "Peter Zijlstra \(Intel\)" <pet...@infradead.org>, "H. Peter Anvin" <h...@zytor.com>, sparclinux <sparcli...@vger.kernel.org>, Tiezhu Yang <yangtiezhu@loongs on.cn>, Miroslav Benes <mbe...@suse.cz>, Chen Zhongjin <chenzhong...@huawei.com>, Ard Biesheuvel <a...@kernel.org>, the arch/x86 maintainers <x...@kernel.org>, Russell King <li...@armlinux.org.uk>, linux-riscv <linux-ri...@lists.infradead.org>, Ingo Molnar <mi...@redhat.com>, Aaron Tomlin <atom...@redhat.com>, Albert Ou <a...@eecs.berkeley.edu>, Heiko Carstens <h...@linux.ibm.com>, Liao Chang <liaocha...@huawei.com>, Paul Walmsley <paul.walms...@sifive.com>, Josh Poimboeuf <jpoim...@kernel.org>, Thomas Richter <tmri...@linux.ibm.com>, "open list:BROADCOM NVRAM DRIVER" <linux-m...@vger.kernel.org>, Changbin Du <changbin...@intel.com>, Palmer Dabbelt <pal...@dabbelt.com>, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>, linux-modu...@vger.kernel.org Errors-To: linuxppc-dev-bounces+archive=mail-archive....@lists.ozlabs.org Sender: "Linuxppc-dev" <linuxppc-dev-bounces+archive=mail-archive....@lists.ozlabs.org>
On Wed, Jun 08, 2022 at 01:26:19PM -0700, Luis Chamberlain wrote: > No, that was removed because it has only one user. That is only part of the story. The other part is that the overall kernel simply does not have any business allocating exutable memory. Executable memory is a very special concept for modules or module-like code like kprobes, and should not be exposed as a general concept. Especially as executable memory really should not also be writable for security reasons. In other words, we should actually never allocate executable memory, every. We might seal memory and then mark it executable after having written to it, which is how modules and kprobes are implemented on all modern Linux ports anyway.
