From: "Liao, Chang" <liaochang1@huawei.com>
To: Oleg Nesterov <oleg@redhat.com>, Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>, <mhiramat@kernel.org>,
<peterz@infradead.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: Thu, 26 Sep 2024 20:06:42 +0800 [thread overview]
Message-ID: <522284d3-9655-3703-00e9-33f358dbc78d@huawei.com> (raw)
In-Reply-To: <20240923105228.GB20793@redhat.com>
在 2024/9/23 18:52, Oleg Nesterov 写道:
> On 09/23, Will Deacon wrote:
>>
>> However, we should use __GFP_ZERO anyway
>> because I don't think it's a good idea to map an uninitialised page into
>> userspace.
>
> Agreed, and imo this even needs a separate "fix info leak" patch.
Do you mean to fill the entire page with CPU specific illegal instructions
in this patch?
>
> Oleg.
>
>
--
BR
Liao, Chang
next prev parent reply other threads:[~2024-09-26 12:06 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
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 [this message]
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=522284d3-9655-3703-00e9-33f358dbc78d@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®