From: Mike Rapoport <rppt@kernel.org>
To: Yaxiong Tian <13327272236@163.com>
Cc: David Hildenbrand <david@redhat.com>,
rafael@kernel.org, pavel@ucw.cz, len.brown@intel.com,
keescook@chromium.org, tony.luck@intel.com, gpiccoli@igalia.com,
akpm@linux-foundation.org, ardb@kernel.org,
wangkefeng.wang@huawei.com, catalin.marinas@arm.com,
will@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
Yaxiong Tian <tianyaxiong@kylinos.cn>,
xiongxin <xiongxin@kylinos.cn>
Subject: Re: [PATCH] PM: hibernate: Fix level3 translation fault in swsusp_save()
Date: Thu, 29 Feb 2024 11:42:23 +0200 [thread overview]
Message-ID: <ZeBRfxQ8WTEVzpfL@kernel.org> (raw)
In-Reply-To: <3399d2af-3d42-4ac1-9b74-8475bec25f7f@163.com>
On Tue, Feb 27, 2024 at 03:51:25PM +0800, Yaxiong Tian wrote:
>
> 在 2024/2/26 17:14, Mike Rapoport 写道:
> > On Mon, Feb 26, 2024 at 09:37:06AM +0100, David Hildenbrand wrote:
> > > On 26.02.24 04:42, Yaxiong Tian wrote:
> > > > From: Yaxiong Tian <tianyaxiong@kylinos.cn>
> > > >
> > > > On ARM64 machines using UEFI, if the linear map is not set (can_set_direct_map()
> > > > return false), swsusp_save() will fail due to can't finding the map table
> > > > under the nomap memory.such as:
> > can_set_direct_map() has nothing to do with presence or absence of the
> > linear map.
> >
> > Do you mean that kernel_page_present() presumes that a page is present when
> > can_set_direct_map() returns false even for NOMAP ranges?
> Yes, in swsusp_save()->copy_data_pages()->page_is_saveable(),
> kernel_page_present() presumes that a page is present when
> can_set_direct_map()
> returns false even for NOMAP ranges.So NOMAP pages will saved in after,and
> then
> cause level3 translation fault in this pages.
So this should be the description of the problem in the changelog rather
than saying "if the linear map is not set (can_set_direct_map() return
false)"
> > > > QEMU ARM64 using UEFI also has the problem by setting can_set_direct_map()
> > > > return false.
> >
> > Huh?
> > Why would you do that?
> >
> I discovered this problem when upgrading from 5.4 to 6.6 using the 5.4
> configuration.
> So I using latest linux-next code,find the problem still exist.To rule out
> the effects
> of a particular machine,I also use qemu to check it.
I believe this can be reproduced if you boot with rodata=off and then
a better description would be something like
This issue can be reproduced in QEMU when booting with rodata=off
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2024-02-29 9:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 3:42 [PATCH] PM: hibernate: Fix level3 translation fault in swsusp_save() Yaxiong Tian
2024-02-26 8:37 ` David Hildenbrand
2024-02-26 9:14 ` Mike Rapoport
2024-02-27 7:51 ` Yaxiong Tian
2024-02-29 9:42 ` Mike Rapoport [this message]
2024-03-01 2:19 ` [PATCH v2] arm64: " Yaxiong Tian
2024-04-12 17:30 ` Catalin Marinas
2024-04-17 2:13 ` Yaxiong Tian
2024-03-01 2:55 ` [PATCH] PM: " Yaxiong Tian
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=ZeBRfxQ8WTEVzpfL@kernel.org \
--to=rppt@kernel.org \
--cc=13327272236@163.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=len.brown@intel.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--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