From: Will Deacon <will@kernel.org>
To: glider@google.com, akpm@linux-foundation.org,
robin.murphy@arm.com, james.morse@arm.com, elver@google.com,
jianyong.wu@arm.com, catalin.marinas@arm.com,
wangkefeng.wang@huawei.com,
Zhenhua Huang <quic_zhenhuah@quicinc.com>,
mark.rutland@arm.com, dvyukov@google.com
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org, quic_guptap@quicinc.com,
quic_pkondeti@quicinc.com, quic_tingweiz@quicinc.com,
kasan-dev@googlegroups.com, linux-mm@kvack.org
Subject: Re: [PATCH v12] mm,kfence: decouple kfence from page granularity mapping judgement
Date: Mon, 27 Mar 2023 17:29:53 +0100 [thread overview]
Message-ID: <167993012079.2285233.18016244231691896258.b4-ty@kernel.org> (raw)
In-Reply-To: <1679066974-690-1-git-send-email-quic_zhenhuah@quicinc.com>
On Fri, 17 Mar 2023 23:29:34 +0800, Zhenhua Huang wrote:
> Kfence only needs its pool to be mapped as page granularity, if it is
> inited early. Previous judgement was a bit over protected. From [1], Mark
> suggested to "just map the KFENCE region a page granularity". So I
> decouple it from judgement and do page granularity mapping for kfence
> pool only. Need to be noticed that late init of kfence pool still requires
> page granularity mapping.
>
> [...]
Applied to arm64 (for-next/mm), thanks!
[1/1] mm,kfence: decouple kfence from page granularity mapping judgement
https://git.kernel.org/arm64/c/bfa7965b33ab
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2023-03-27 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 15:29 Zhenhua Huang
2023-03-27 16:29 ` Will Deacon [this message]
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=167993012079.2285233.18016244231691896258.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=james.morse@arm.com \
--cc=jianyong.wu@arm.com \
--cc=kasan-dev@googlegroups.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=quic_guptap@quicinc.com \
--cc=quic_pkondeti@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_zhenhuah@quicinc.com \
--cc=robin.murphy@arm.com \
--cc=wangkefeng.wang@huawei.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