From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: Andi Kleen <ak@linux.intel.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Mike Rapoport <rppt@linux.ibm.com>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH v4 5/7] arch/x86: kprobes: Use text_alloc() in alloc_insn_page()
Date: Fri, 24 Jul 2020 01:16:41 +0300 [thread overview]
Message-ID: <20200723221641.GA12405@linux.intel.com> (raw)
In-Reply-To: <20200717030422.679972-6-jarkko.sakkinen@linux.intel.com>
On Fri, Jul 17, 2020 at 06:04:19AM +0300, Jarkko Sakkinen wrote:
> Use text_alloc() as part of the arch specific implementation for
> alloc_insn_page().
>
> Cc: Andi Kleen <ak@linux.intel.com>
> Cc: Masami Hiramatsu <mhiramat@kernel.org>
> Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>Im
> ---
> arch/x86/kernel/kprobes/core.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/arch/x86/kernel/kprobes/core.c b/arch/x86/kernel/kprobes/core.c
> index ada39ddbc922..0f20a3e52a06 100644
> --- a/arch/x86/kernel/kprobes/core.c
> +++ b/arch/x86/kernel/kprobes/core.c
> @@ -423,7 +423,7 @@ void *alloc_insn_page(void)
> {
> void *page;
>
> - page = module_alloc(PAGE_SIZE);
> + page = text_alloc(PAGE_SIZE);
> if (!page)
> return NULL;
>
> @@ -443,12 +443,6 @@ void *alloc_insn_page(void)
> return page;
> }
>
> -/* Recover page to RW mode before releasing it */
> -void free_insn_page(void *page)
> -{
> - module_memfree(page);
This must be a mistake. Should be just changed to call text_memfree().
Probably just my clumsiness when refactoring the series.
> -}
> -
> static int arch_copy_kprobe(struct kprobe *p)
> {
> struct insn insn;
> --
> 2.25.1
>
/Jarkko
next prev parent reply other threads:[~2020-07-23 22:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 3:04 [PATCH v4 0/7] arch/x86: kprobes: Remove MODULES dependency Jarkko Sakkinen
2020-07-17 3:04 ` [PATCH v4 1/7] module: Add lock_modules() and unlock_modules() Jarkko Sakkinen
2020-07-17 3:04 ` [PATCH v4 2/7] kprobes: Use " Jarkko Sakkinen
2020-07-17 3:04 ` [PATCH v4 3/7] vmalloc: Add text_alloc() and text_free() Jarkko Sakkinen
2020-07-17 5:33 ` kernel test robot
2020-07-17 5:33 ` kernel test robot
2020-07-17 8:52 ` Masami Hiramatsu
2020-07-23 22:24 ` Jarkko Sakkinen
2020-07-18 16:23 ` Mike Rapoport
2020-07-20 12:01 ` Masami Hiramatsu
2020-07-23 22:28 ` Jarkko Sakkinen
2020-07-24 10:13 ` Mike Rapoport
2020-07-24 23:31 ` Jarkko Sakkinen
2020-07-24 23:40 ` Jarkko Sakkinen
2020-07-17 3:04 ` [PATCH v4 4/7] arch/x86: Implement " Jarkko Sakkinen
2020-07-17 3:04 ` [PATCH v4 5/7] arch/x86: kprobes: Use text_alloc() in alloc_insn_page() Jarkko Sakkinen
2020-07-23 22:16 ` Jarkko Sakkinen [this message]
2020-07-17 3:04 ` [PATCH v4 6/7] kprobes: Use text_alloc() and text_free() Jarkko Sakkinen
2020-07-17 3:04 ` [PATCH v4 7/7] kprobes: Flag out CONFIG_MODULES dependent code Jarkko Sakkinen
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=20200723221641.GA12405@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rppt@linux.ibm.com \
--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
Powered by JetHome