From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bugzilla-daemon@kernel.org, parag.lkml@gmail.com,
linux-mm@kvack.org, dri-devel@lists.freedesktop.org
Subject: Re: [Bug 215807] Bad page state in process systemd-udevd
Date: Tue, 12 Apr 2022 22:17:54 +0100 [thread overview]
Message-ID: <YlXsgjmjrkvnjXQB@casper.infradead.org> (raw)
In-Reply-To: <20220412140804.e73d55d5d192f2198c9278ec@linux-foundation.org>
On Tue, Apr 12, 2022 at 02:08:04PM -0700, Andrew Morton wrote:
> hm, that's my third `bad page' report in three emails. But I'm not
> seeing a pattern - this one might be a DRM thing.
I noticed it was an order-9 page and was set to take responsibility
for it, but it's clearly not a filesystem page, but a DRM page.
Let me help decode this for the benefit of the DRM folks.
> > [ 8.453363] amdgpu: Topology: Add CPU node
> > [ 8.467169] BUG: Bad page state in process systemd-udevd pfn:11b403
> > [ 8.467180] fbcon: Taking over console
> > [ 8.467188] page:000000002cc06944 refcount:0 mapcount:0
> > mapping:0000000000000000 index:0x3 pfn:0x11b403
> > [ 8.467195] head:00000000aa25e58e order:9 compound_mapcount:0
> > compound_pincount:0
> > [ 8.467198] flags: 0x17ffffc0010000(head|node=0|zone=2|lastcpupid=0x1fffff)
> > [ 8.467205] raw: 0017ffffc0000000 fffff2da846d0001 fffff2da846d00c8
> > 0000000000000000
> > [ 8.467208] raw: 0000000000000000 0000000000000000 00000000ffffffff
> > 0000000000000000
> > [ 8.467210] head: 0017ffffc0010000 0000000000000000 dead000000000122
> > 0000000000000000
> > [ 8.467212] head: 0000000000000000 0000000000000000 00000000ffffffff
> > 0000000000000000
> > [ 8.467214] page dumped because: corrupted mapping in tail page
Tail pages are all supposed to have page->mapping == TAIL_MAPPING
(0x400 + POISON_POINTER_DELTA). This one has page->mapping == NULL.
I say "all", but tail pages 1 and 2 aren't checked because those
get other useful things stored in them instead. This is tail page
number 3, so it's the first one checked.
So DRM has probably been overly enthusiastic about cleaning up
something. Hope that's helpful!
prev parent reply other threads:[~2022-04-12 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-215807-27@https.bugzilla.kernel.org/>
[not found] ` <bug-215807-27-EqWyiHqWrc@https.bugzilla.kernel.org/>
2022-04-12 21:08 ` Andrew Morton
2022-04-12 21:17 ` Matthew Wilcox [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=YlXsgjmjrkvnjXQB@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-mm@kvack.org \
--cc=parag.lkml@gmail.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