From: Matthew Wilcox <willy@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [regression 6.14-rc2 + xfs-for-next] Bad page state at unmount
Date: Wed, 19 Feb 2025 04:36:04 +0000 [thread overview]
Message-ID: <Z7VftAeqEgTwUyx_@casper.infradead.org> (raw)
In-Reply-To: <Z7VU9QX8MrmZVSrU@dread.disaster.area>
On Wed, Feb 19, 2025 at 02:50:13PM +1100, Dave Chinner wrote:
> Hi folks,
>
> I hit this running check-parallel a moment ago:
>
> [80180.074658] BUG: Bad page cache in process umount pfn:7655f4
> [80180.077259] page: refcount:9 mapcount:1 mapping:00000000ecd1b54a index:0x0 pfn:0x7655f4
> [80180.080573] head: order:2 mapcount:4 entire_mapcount:0 nr_pages_mapped:4 pincount:0
> [80180.083615] memcg:ffff888104f36000
> [80180.084977] aops:xfs_address_space_operations ino:84
> [80180.087175] flags: 0x17ffffc000016d(locked|referenced|uptodate|lru|active|head|node=0|zone=2|lastcpupid=0x1fffff)
> [80180.091380] raw: 0017ffffc000016d ffffea001745c648 ffffea0012b1da08 ffff8891726dae98
> [80180.094469] raw: 0000000000000000 0000000000000000 0000000900000000 ffff888104f36000
> [80180.097740] head: 0017ffffc000016d ffffea001745c648 ffffea0012b1da08 ffff8891726dae98
> [80180.100988] head: 0000000000000000 0000000000000000 0000000900000000 ffff888104f36000
> [80180.104129] head: 0017ffffc0000202 ffffea001d957d01 ffffffff00000003 0000000000000004
> [80180.107232] head: 0000000000000004 0000000000000000 0000000000000000 0000000000000000
> [80180.110338] page dumped because: still mapped when deleted
Do you have CONFIG_PT_RECLAIM enabled? If so, it's buggy (see linux-mm
for a fix if you don't want to disable it).
next prev parent reply other threads:[~2025-02-19 4:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 3:50 [regression 6.14-rc2 + xfs-for-next] Bad page state at unmount Dave Chinner
2025-02-19 3:59 ` Darrick J. Wong
2025-02-19 4:36 ` Matthew Wilcox [this message]
2025-02-19 5:39 ` Dave Chinner
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=Z7VftAeqEgTwUyx_@casper.infradead.org \
--to=willy@infradead.org \
--cc=david@fromorbit.com \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.