From: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
oleg@redhat.com, rostedt@goodmis.org,
linux-kernel@vger.kernel.org, paulus@samba.org,
sandipan@linux.ibm.com, jniethe5@gmail.com,
naveen.n.rao@linux.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc/uprobes: Validation for prefixed instruction
Date: Mon, 8 Feb 2021 16:43:14 +0530 [thread overview]
Message-ID: <b8f629b7-ea04-a77a-10bb-dd4bdcd231f7@linux.ibm.com> (raw)
In-Reply-To: <20210204130821.GK210@DESKTOP-TDPLP67.localdomain>
On 2/4/21 6:38 PM, Naveen N. Rao wrote:
> On 2021/02/04 04:17PM, Ravi Bangoria wrote:
>> Don't allow Uprobe on 2nd word of a prefixed instruction. As per
>> ISA 3.1, prefixed instruction should not cross 64-byte boundary.
>> So don't allow Uprobe on such prefixed instruction as well.
>>
>> There are two ways probed instruction is changed in mapped pages.
>> First, when Uprobe is activated, it searches for all the relevant
>> pages and replace instruction in them. In this case, if we notice
>> that probe is on the 2nd word of prefixed instruction, error out
>> directly. Second, when Uprobe is already active and user maps a
>> relevant page via mmap(), instruction is replaced via mmap() code
>> path. But because Uprobe is invalid, entire mmap() operation can
>> not be stopped. In this case just print an error and continue.
>>
>> Signed-off-by: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
>> ---
>> v1: http://lore.kernel.org/r/20210119091234.76317-1-ravi.bangoria@linux.ibm.com
>> v1->v2:
>> - Instead of introducing new arch hook from verify_opcode(), use
>> existing hook arch_uprobe_analyze_insn().
>> - Add explicit check for prefixed instruction crossing 64-byte
>> boundary. If probe is on such instruction, throw an error.
>>
>> arch/powerpc/kernel/uprobes.c | 66 ++++++++++++++++++++++++++++++++++-
>> 1 file changed, 65 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/powerpc/kernel/uprobes.c b/arch/powerpc/kernel/uprobes.c
>> index e8a63713e655..485d19a2a31f 100644
>> --- a/arch/powerpc/kernel/uprobes.c
>> +++ b/arch/powerpc/kernel/uprobes.c
>> @@ -7,6 +7,7 @@
>> * Adapted from the x86 port by Ananth N Mavinakayanahalli <ananth@in.ibm.com>
>> */
>> #include <linux/kernel.h>
>> +#include <linux/highmem.h>
>> #include <linux/sched.h>
>> #include <linux/ptrace.h>
>> #include <linux/uprobes.h>
>> @@ -28,6 +29,69 @@ bool is_trap_insn(uprobe_opcode_t *insn)
>> return (is_trap(*insn));
>> }
>>
>> +#ifdef CONFIG_PPC64
>> +static int get_instr(struct mm_struct *mm, unsigned long addr, u32 *instr)
>> +{
>> + struct page *page;
>> + struct vm_area_struct *vma;
>> + void *kaddr;
>> + unsigned int gup_flags = FOLL_FORCE | FOLL_SPLIT_PMD;
>> +
>> + if (get_user_pages_remote(mm, addr, 1, gup_flags, &page, &vma, NULL) <= 0)
>> + return -EINVAL;
>> +
>> + kaddr = kmap_atomic(page);
>> + *instr = *((u32 *)(kaddr + (addr & ~PAGE_MASK)));
>> + kunmap_atomic(kaddr);
>> + put_page(page);
>> + return 0;
>> +}
>> +
>> +static int validate_prefixed_instr(struct mm_struct *mm, unsigned long addr)
>> +{
>> + struct ppc_inst inst;
>> + u32 prefix, suffix;
>> +
>> + /*
>> + * No need to check if addr is pointing to beginning of the
>> + * page. Even if probe is on a suffix of page-unaligned
>> + * prefixed instruction, hw will raise exception and kernel
>> + * will send SIGBUS.
>> + */
>> + if (!(addr & ~PAGE_MASK))
>> + return 0;
>> +
>> + if (get_instr(mm, addr, &prefix) < 0)
>> + return -EINVAL;
>> + if (get_instr(mm, addr + 4, &suffix) < 0)
>> + return -EINVAL;
>> +
>> + inst = ppc_inst_prefix(prefix, suffix);
>> + if (ppc_inst_prefixed(inst) && (addr & 0x3F) == 0x3C) {
>> + printk_ratelimited("Cannot register a uprobe on 64 byte "
> ^^^^^^^^^^^^^^^^^^ pr_info_ratelimited()
>
> It should be sufficient to check the primary opcode to determine if it
> is a prefixed instruction. You don't have to read the suffix. I see that
> we don't have a helper to do this currently, so you could do:
>
> if (ppc_inst_primary_opcode(ppc_inst(prefix)) == 1)
Ok.
>
> In the future, it might be worthwhile to add IS_PREFIX() as a macro
> similar to IS_MTMSRD() if there are more such uses.
>
> Along with this, if you also add the below to the start of this
> function, you can get rid of the #ifdef:
>
> if (!IS_ENABLED(CONFIG_PPC64))
> return 0;
Yeah this is better.
Thanks for the review, Naveen!
Ravi
next prev parent reply other threads:[~2021-02-08 11:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 10:47 [PATCH v2] powerpc/uprobes: Validation for prefixed instruction Ravi Bangoria
2021-02-04 10:49 ` Ravi Bangoria
2021-02-04 13:15 ` Naveen N. Rao
2021-02-08 11:08 ` Ravi Bangoria
2021-02-04 14:19 ` Ananth N Mavinakayanahalli
2021-02-04 13:08 ` Naveen N. Rao
2021-02-04 16:12 ` Naveen N. Rao
2021-02-08 11:10 ` Ravi Bangoria
2021-02-08 11:13 ` Ravi Bangoria [this message]
2021-02-06 18:06 ` Oleg Nesterov
2021-02-08 11:06 ` Ravi Bangoria
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=b8f629b7-ea04-a77a-10bb-dd4bdcd231f7@linux.ibm.com \
--to=ravi.bangoria@linux.ibm.com \
--cc=jniethe5@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=oleg@redhat.com \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.org \
--cc=sandipan@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).