From: Alex Shi <seakeel@gmail.com>
To: Dongliang Mu <dzm91@hust.edu.cn>,
si.yanteng@linux.dev, alexs@kernel.org, corbet@lwn.net,
Yanteng Si <siyanteng@loongson.cn>
Cc: hust-os-kernel-patches@googlegroups.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] docs/zh_CN: update the translation of mm/page_table_check.rst
Date: Tue, 22 Oct 2024 09:44:39 +0800 [thread overview]
Message-ID: <0a794201-6886-482d-8533-dd7fd9e59de9@gmail.com> (raw)
In-Reply-To: <68b62a5713d5a465f09226c1a607dee7ec76a6aa.1729327831.git.dzm91@hust.edu.cn>
Reviewed-by: Alex Shi <alexs@kernel.org>
On 10/19/24 16:54, Dongliang Mu wrote:
> Update to commit 8430557fc584 ("mm/page_table_check: support
> userfault wr-protect entries")
>
> scripts/checktransupdate.py reports:
>
> Documentation/translations/zh_CN/mm/page_table_check.rst
> commit 8430557fc584 ("mm/page_table_check: support userfault wr-protect
> entries")
> commit 81a31a860bb6 ("mm: page_table_check: Make it dependent on
> EXCLUSIVE_SYSTEM_RAM")
> commit ee86588960e2 ("docs/mm: remove useless markup")
> 3 commits needs resolving in total
>
> Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn>
> ---
> .../translations/zh_CN/mm/page_table_check.rst | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/Documentation/translations/zh_CN/mm/page_table_check.rst b/Documentation/translations/zh_CN/mm/page_table_check.rst
> index e8077310a76c..dc34570dceff 100644
> --- a/Documentation/translations/zh_CN/mm/page_table_check.rst
> +++ b/Documentation/translations/zh_CN/mm/page_table_check.rst
> @@ -54,3 +54,16 @@
>
> 可以选择用PAGE_TABLE_CHECK_ENFORCED来构建内核,以便在没有额外的内核参数的情况下获得页表
> 支持。
> +
> +实现注意事项
> +============
> +
> +我们特意决定不使用 VMA 信息,以避免依赖于 MM 状态(除了有限的 “struct page” 信息)。页表检查
> +独立于 Linux-MM 状态机,它验证用户可访问的页面不会被错误地共享。
> +
> +PAGE_TABLE_CHECK 依赖于 EXCLUSIVE_SYSTEM_RAM。原因在于,若没有 EXCLUSIVE_SYSTEM_RAM,
> +用户被允许通过 /dev/mem 将任意物理内存区域映射到用户空间。同时,页面可能在映射到用户空间期间
> +改变自己的属性(例如,从匿名页面变为命名页面),导致页表检查检测到“损坏”。
> +
> +即使有 EXCLUSIVE_SYSTEM_RAM,I/O 页面可能仍然被允许通过 /dev/mem 映射。然而,这些页面始终
> +被视为命名页面,所以它们不会破坏页表检查中使用的逻辑。
next prev parent reply other threads:[~2024-10-22 1:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1729327831.git.dzm91@hust.edu.cn>
2024-10-19 8:54 ` [PATCH 1/6] docs/zh_CN: update the translation of mm/hmm.rst Dongliang Mu
2024-10-22 1:43 ` Alex Shi
2024-10-22 2:02 ` Alex Shi
2024-10-22 3:28 ` Alex Shi
2024-10-19 8:54 ` [PATCH 2/6] docs/zh_CN: update the translation of mm/active_mm.rst Dongliang Mu
2024-10-22 1:43 ` Alex Shi
2024-10-19 8:54 ` [PATCH 3/6] docs/zh_CN: update the translation of mm/admon/faq.rst Dongliang Mu
2024-10-22 1:43 ` Alex Shi
2024-10-19 8:54 ` [PATCH 4/6] docs/zh_CN: update the translation of mm/overcommit-accounting.rst Dongliang Mu
2024-10-22 1:44 ` Alex Shi
2024-10-19 8:54 ` [PATCH 5/6] docs/zh_CN: update the translation of mm/page_table_check.rst Dongliang Mu
2024-10-22 1:44 ` Alex Shi [this message]
2024-10-19 8:54 ` [PATCH 6/6] docs/zh_CN: update the translation of mm/page_owner.rst Dongliang Mu
2024-10-22 1:44 ` Alex Shi
2024-10-24 21:45 ` [PATCH 0/6] update the translation of partial files in mm Jonathan Corbet
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=0a794201-6886-482d-8533-dd7fd9e59de9@gmail.com \
--to=seakeel@gmail.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=si.yanteng@linux.dev \
--cc=siyanteng@loongson.cn \
/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®