linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	"fstests@vger.kernel.org" <fstests@vger.kernel.org>
Subject: Re: Btrfs crash on generic/437 on x86_64
Date: Mon, 10 Feb 2025 03:59:54 +0000	[thread overview]
Message-ID: <Z6l5uhuhAJ3Vepcq@casper.infradead.org> (raw)
In-Reply-To: <a33deb4e-3f6c-4a5e-9da9-ad403a858aca@gmx.com>

On Mon, Feb 10, 2025 at 02:13:53PM +1030, Qu Wenruo wrote:
> 在 2025/2/10 14:01, Matthew Wilcox 写道:
> > > [   58.305921] BTRFS info (device dm-0): using free-space-tree
> > > [   58.319296] run fstests generic/437 at 2025-02-10 13:24:19
> > > [   59.283069] BUG: Bad rss-counter state mm:0000000048578720
> > > type:MM_FILEPAGES val:1

> > We need to figure out how we came to not unmap the page from the page
> > tables originally.  Looking through the merge log of the mm tree, my
> > suspicion falls on the following patchsets:
> > 
> >         - "synchronously scan and reclaim empty user PTE pages" from Qi Zheng
> >           addresses an issue where "huge" amounts of pte pagetables are
> >           accumulated:

https://lore.kernel.org/linux-mm/2766D04E-5A04-4BF6-A2A3-5683A3054973@nvidia.com/
looks like a similar splat with the problem narrowed down to the reclaim
PTE pages patchset.


      reply	other threads:[~2025-02-10  3:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10  3:10 Qu Wenruo
2025-02-10  3:31 ` Matthew Wilcox
2025-02-10  3:43   ` Qu Wenruo
2025-02-10  3:59     ` 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=Z6l5uhuhAJ3Vepcq@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=quwenruo.btrfs@gmx.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