From: Peter Zijlstra <peterz@infradead.org>
To: Song Liu <song@kernel.org>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-modules@vger.kernel.org,
mcgrof@kernel.org, rostedt@goodmis.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, mhiramat@kernel.org,
naveen.n.rao@linux.ibm.com, davem@davemloft.net,
anil.s.keshavamurthy@intel.com, keescook@chromium.org,
hch@infradead.org, dave@stgolabs.net, daniel@iogearbox.net,
kernel-team@fb.com, x86@kernel.org, dave.hansen@linux.intel.com,
rick.p.edgecombe@intel.com, akpm@linux-foundation.org
Subject: Re: [PATCH bpf-next 1/3] mm/vmalloc: introduce vmalloc_exec which allocates RO+X memory
Date: Wed, 13 Jul 2022 11:53:15 +0200 [thread overview]
Message-ID: <Ys6WCwU0VlTe2zIf@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20220713071846.3286727-2-song@kernel.org>
On Wed, Jul 13, 2022 at 12:18:44AM -0700, Song Liu wrote:
> +/**
> + * vmalloc_exec - allocate RO+X memory in kernel text space
> + * @size: allocation size
> + *
> + * Allocate @size of RO+X memory in kernel text space. This memory can be
> + * used to serve dynamic kernel text, such as BPF programs.
> + *
> + * The memory allocated is filled illegal instructions.
> + *
> + * Return: pointer to the allocated memory or %NULL on error
> + */
> +void *vmalloc_exec(size_t size)
> +{
> + return vmalloc_exec_pack_alloc(size);
> +}
> +EXPORT_SYMBOL_GPL(vmalloc_exec);
NAK! modules do *NOT* get to allocate text.
next parent reply other threads:[~2022-07-13 9:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220713071846.3286727-1-song@kernel.org>
[not found] ` <20220713071846.3286727-2-song@kernel.org>
2022-07-13 9:53 ` Peter Zijlstra [this message]
2022-07-13 10:08 ` Christoph Hellwig
2022-07-13 15:49 ` Song Liu
2022-07-14 4:23 ` Christoph Hellwig
2022-07-14 4:54 ` Song Liu
2022-07-14 18:15 ` Uladzislau Rezki
2022-07-15 0:24 ` Song Liu
2022-07-13 10:20 ` Peter Zijlstra
2022-07-13 15:48 ` Song Liu
2022-07-13 20:26 ` Peter Zijlstra
2022-07-13 21:20 ` Song Liu
2022-07-14 10:10 ` Peter Zijlstra
2022-07-14 5:16 ` Christoph Hellwig
2022-07-14 7:26 ` Peter Zijlstra
2022-08-05 5:29 ` Song Liu
2022-08-05 5:29 ` Song Liu
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=Ys6WCwU0VlTe2zIf@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=keescook@chromium.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=naveen.n.rao@linux.ibm.com \
--cc=rick.p.edgecombe@intel.com \
--cc=rostedt@goodmis.org \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--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