From: Yang Shi <shy828301@gmail.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Matthew Wilcox" <willy@infradead.org>,
"Linux MM" <linux-mm@kvack.org>,
"HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>,
"Mike Kravetz" <mike.kravetz@oracle.com>,
bp@alien8.de, "Miaohe Lin" <linmiaohe@huawei.com>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: unhandlable pages
Date: Mon, 21 Mar 2022 14:07:28 -0700 [thread overview]
Message-ID: <CAHbLzkrBHdCTE8U364WSLxCpumwkjuZOkZLjukOEHHF0ksJseA@mail.gmail.com> (raw)
In-Reply-To: <Yji1uY0YfJriC4sI@agluck-desk3.sc.intel.com>
On Mon, Mar 21, 2022 at 10:28 AM Luck, Tony <tony.luck@intel.com> wrote:
>
> On Mon, Mar 21, 2022 at 05:21:05PM +0000, Matthew Wilcox wrote:
> > On Mon, Mar 21, 2022 at 10:17:29AM -0700, Luck, Tony wrote:
> > > Validation folks are seeing this on a v5.16 kernel. I don't
> > > see any changes in v5.17 that look like they address it.
> > >
> > > Mar 04 14:05:05 JF5300-07B181T kernel: page:00000000696b0b6a refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x195cda44
> > > Mar 04 14:05:05 JF5300-07B181T kernel: flags: 0x57ffffc0801000(reserved|hwpoison|node=1|zone=2|lastcpupid=0x1fffff)
> > > Mar 04 14:05:05 JF5300-07B181T kernel: raw: 0057ffffc0801000 ffff6ea817369108 ffff6ea817369108 0000000000000000
> > > Mar 04 14:05:05 JF5300-07B181T kernel: raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000
> > > Mar 04 14:05:05 JF5300-07B181T kernel: page dumped because: hwpoison: unhandlable page
> > > Mar 04 14:05:05 JF5300-07B181T kernel: Memory failure: 0x195cda44: recovery action for unknown page: Ignored
> > >
> > > Som debugging shows this is an anon page (expected ... that's the
> > > type of page where the error was injected. They see shake_page()
> > > called three times, but it doesn't change anything, so the page
> > > is reported as unhandlable.
> >
> > Uhm, that's not PageAnon. page->mapping is NULL, and anon pages have
> > the bottom bit set with the rest of the page->mapping pointing to its
> > anon_vma. Why do you think it's an anon page?
>
> Sorry. I didn't do that decode ... just copied what was in the internal
> report. If it isn't anon, then does that page dump give info on what
> type the page is?
As Willy said we can't tell what type the page is. Per the dumped
information, the page has:
- 1 refcount, likely get from hwpoison
- 0 mapcount, unmapped and not unmapped by hwpoison since
dump_page() is called before that,
- NULL mapping
- PG_reserved flag is set and no other flag is set
So I just can say it is very unlikely to be an anonymous page. It is
not slab either. And neither anonymous/page cache nor slab should be
reserved flag set, so it should be some other types.
>
> -Tony
next prev parent reply other threads:[~2022-03-21 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 17:17 Luck, Tony
2022-03-21 17:21 ` Matthew Wilcox
2022-03-21 17:28 ` Luck, Tony
2022-03-21 17:32 ` Matthew Wilcox
2022-03-21 21:07 ` Yang Shi [this message]
2022-03-21 21:19 ` Luck, Tony
2022-03-22 0:10 ` Jane Chu
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=CAHbLzkrBHdCTE8U364WSLxCpumwkjuZOkZLjukOEHHF0ksJseA@mail.gmail.com \
--to=shy828301@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@nec.com \
--cc=tony.luck@intel.com \
--cc=willy@infradead.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