From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Russell Currey <ruscur@russell.cc>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/7] powerpc/kprobes: Mark newly allocated probes as RO
Date: Mon, 3 Feb 2020 08:00:26 +0100 [thread overview]
Message-ID: <d6451710-3582-305b-ad81-018a1ea0ef3d@c-s.fr> (raw)
In-Reply-To: <3078df74c232e54aef3e8bb3523587a3053ab0ec.camel@russell.cc>
Le 03/02/2020 à 05:50, Russell Currey a écrit :
> On Fri, 2020-01-31 at 13:34 +0000, Christophe Leroy wrote:
>> With CONFIG_STRICT_KERNEL_RWX=y and CONFIG_KPROBES=y, there will be
>> one
>> W+X page at boot by default. This can be tested with
>> CONFIG_PPC_PTDUMP=y and CONFIG_PPC_DEBUG_WX=y set, and checking the
>> kernel log during boot.
>>
>> powerpc doesn't implement its own alloc() for kprobes like other
>> architectures do, but we couldn't immediately mark RO anyway since we
>> do
>> a memcpy to the page we allocate later. After that, nothing should
>> be
>> allowed to modify the page, and write permissions are removed well
>> before the kprobe is armed.
>>
>> The memcpy() would fail if >1 probes were allocated, so use
>> patch_instruction() instead which is safe for RO.
>>
>> Reviewed-by: Daniel Axtens <dja@axtens.net>
>> Signed-off-by: Russell Currey <ruscur@russell.cc>
>> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
>> ---
>> v2: removed the redundant flush
>> ---
>> arch/powerpc/kernel/kprobes.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/powerpc/kernel/kprobes.c
>> b/arch/powerpc/kernel/kprobes.c
>> index 2d27ec4feee4..d3e594e6094c 100644
>> --- a/arch/powerpc/kernel/kprobes.c
>> +++ b/arch/powerpc/kernel/kprobes.c
>> @@ -24,6 +24,7 @@
>> #include <asm/sstep.h>
>> #include <asm/sections.h>
>> #include <linux/uaccess.h>
>> +#include <linux/set_memory.h>
>>
>> DEFINE_PER_CPU(struct kprobe *, current_kprobe) = NULL;
>> DEFINE_PER_CPU(struct kprobe_ctlblk, kprobe_ctlblk);
>> @@ -124,13 +125,12 @@ int arch_prepare_kprobe(struct kprobe *p)
>> }
>>
>> if (!ret) {
>> - memcpy(p->ainsn.insn, p->addr,
>> - MAX_INSN_SIZE *
>> sizeof(kprobe_opcode_t));
>> + patch_instruction(p->ainsn.insn, *p->addr);
>> p->opcode = *p->addr;
>> - flush_icache_range((unsigned long)p->ainsn.insn,
>> - (unsigned long)p->ainsn.insn +
>> sizeof(kprobe_opcode_t));
>> }
>>
>> + set_memory_ro((unsigned long)p->ainsn.insn, 1);
>> +
>
>
> Since this can be called multiple times on the same page, can avoid by
> implementing:
>
> void *alloc_insn_page(void)
> {
> void *page;
>
> page = vmalloc_exec(PAGE_SIZE);
> if (page)
> set_memory_ro((unsigned long)page, 1);
>
> return page;
> }
>
> Which is pretty much the same as what's in arm64. Works for me and
> passes ftracetest, I was originally doing this but cut it because it
> broke with the memcpy, but works with patch_instruction().
>
>> p->ainsn.boostable = 0;
>> return ret;
>> }
Ok. I'll send out v3 as patch 1 fails on PPC64, so I'll take that in.
Christophe
next prev parent reply other threads:[~2020-02-03 7:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 13:34 [PATCH v2 1/7] powerpc/mm: Implement set_memory() routines Christophe Leroy
2020-01-31 13:34 ` [PATCH v2 2/7] powerpc/kprobes: Mark newly allocated probes as RO Christophe Leroy
2020-02-03 4:50 ` Russell Currey
2020-02-03 7:00 ` Christophe Leroy [this message]
2020-01-31 13:34 ` [PATCH v2 3/7] powerpc/mm/ptdump: debugfs handler for W+X checks at runtime Christophe Leroy
2020-01-31 13:34 ` [PATCH v2 4/7] powerpc: Set ARCH_HAS_STRICT_MODULE_RWX Christophe Leroy
2020-01-31 13:34 ` [PATCH v2 5/7] powerpc/configs: Enable STRICT_MODULE_RWX in skiroot_defconfig Christophe Leroy
2020-01-31 13:34 ` [PATCH v2 6/7] powerpc/mm: implement set_memory_attr() Christophe Leroy
2020-01-31 13:34 ` [PATCH v2 7/7] powerpc/32: use set_memory_attr() Christophe Leroy
2020-02-03 3:45 ` [PATCH v2 1/7] powerpc/mm: Implement set_memory() routines kbuild test robot
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=d6451710-3582-305b-ad81-018a1ea0ef3d@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=ruscur@russell.cc \
/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