From: "Liao, Chang" <liaochang1@huawei.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: <mhiramat@kernel.org>, <peterz@infradead.org>,
<catalin.marinas@arm.com>, <will@kernel.org>,
<mark.rutland@arm.com>, <linux-kernel@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: uprobes: Optimize cache flushes for xol slot
Date: Fri, 20 Sep 2024 16:58:31 +0800 [thread overview]
Message-ID: <41fdfc47-4161-d2e4-6528-4079b660424f@huawei.com> (raw)
In-Reply-To: <20240919141824.GB12149@redhat.com>
在 2024/9/19 22:18, Oleg Nesterov 写道:
> On 09/19, Liao Chang wrote:
>>
>> --- a/arch/arm64/kernel/probes/uprobes.c
>> +++ b/arch/arm64/kernel/probes/uprobes.c
>> @@ -17,12 +17,16 @@ void arch_uprobe_copy_ixol(struct page *page, unsigned long vaddr,
>> void *xol_page_kaddr = kmap_atomic(page);
>> void *dst = xol_page_kaddr + (vaddr & ~PAGE_MASK);
>>
>> + if (!memcmp(dst, src, len))
>> + goto done;
>
> can't really comment, I know nothing about arm64...
>
> but don't we need to change __create_xol_area()
>
> - area->page = alloc_page(GFP_HIGHUSER);
> + area->page = alloc_page(GFP_HIGHUSER | __GFP_ZERO);
>
> to avoid the false positives?
Indeed, it would be safer.
Could we tolerate these false positives? Even if the page are not reset
to zero bits, if the existing bits are the same as the instruction being
copied, it still can execute the correct instruction.
>
> Oleg.
>
>
--
BR
Liao, Chang
next prev parent reply other threads:[~2024-09-20 8:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 12:17 Liao Chang
2024-09-19 14:18 ` Oleg Nesterov
2024-09-20 8:58 ` Liao, Chang [this message]
2024-09-20 11:03 ` Oleg Nesterov
2024-09-20 15:32 ` Catalin Marinas
2024-09-20 17:32 ` Oleg Nesterov
2024-09-22 14:09 ` Will Deacon
2024-09-22 14:39 ` Oleg Nesterov
2024-09-23 11:16 ` Liao, Chang
2024-09-23 1:57 ` Liao, Chang
2024-09-23 7:18 ` Will Deacon
2024-09-23 10:52 ` Oleg Nesterov
2024-09-26 12:06 ` Liao, Chang
2024-09-26 16:08 ` Oleg Nesterov
2024-09-23 11:16 ` Liao, Chang
2024-09-23 16:03 ` Catalin Marinas
2024-11-06 9:55 ` Liao, Chang
2024-11-07 18:35 ` Catalin Marinas
2024-11-08 16:49 ` Catalin Marinas
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=41fdfc47-4161-d2e4-6528-4079b660424f@huawei.com \
--to=liaochang1@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=will@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
all inboxes | Powered by JetHome®