From: Catalin Marinas <catalin.marinas@arm.com>
To: will@kernel.org, rppt@kernel.org, Yaxiong Tian <tianyaxiong@kylinos.cn>
Cc: keescook@chromium.org, tony.luck@intel.com, gpiccoli@igalia.com,
akpm@linux-foundation.org, ryan.roberts@arm.com,
wangkefeng.wang@huawei.com, ardb@kernel.org, david@redhat.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
xiongxin <xiongxin@kylinos.cn>
Subject: Re: [PATCH v3] arm64: hibernate: Fix level3 translation fault in swsusp_save()
Date: Fri, 19 Apr 2024 17:44:08 +0100 [thread overview]
Message-ID: <171354500626.1387030.2608430533776260920.b4-ty@arm.com> (raw)
In-Reply-To: <20240417025248.386622-1-tianyaxiong@kylinos.cn>
On Wed, 17 Apr 2024 10:52:48 +0800, Yaxiong Tian wrote:
> On ARM64 machines using UEFI, if can_set_direct_map() return false by
> setting some CONFIGS in kernel build or grub,such as
> NO CONFIG_DEBUG_PAGEALLOC_ENABLE_DEFAULT、NO CONFIG_KFENCE
> NO CONFIG_RODATA_FULL_DEFAULT_ENABLED.Also with setting rodata=off、
> debug_pagealloc=off in grub and NO CONFIG_KFENCE.
> swsusp_save() will fail due to can't finding the map table under the
> nomap memory.such as:
>
> [...]
Applied to arm64 (for-next/fixes), thanks! I tidied up the commit log a
bit.
[1/1] arm64: hibernate: Fix level3 translation fault in swsusp_save()
https://git.kernel.org/arm64/c/50449ca66cc5
--
Catalin
prev parent reply other threads:[~2024-04-19 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 2:52 [PATCH v3] arm64: hibernate: Fix level3 translation fault in swsusp_save() Yaxiong Tian
2024-04-19 15:01 ` Mike Rapoport
2024-04-19 16:44 ` Catalin Marinas [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=171354500626.1387030.2608430533776260920.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=david@redhat.com \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=tianyaxiong@kylinos.cn \
--cc=tony.luck@intel.com \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
--cc=xiongxin@kylinos.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).