From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Matthew Wilcox <willy@infradead.org>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
linux-mm@kvack.org
Subject: Re: Multi-page folio issues in 5.19-rc4 (was [PATCH v3 25/25] xfs: Support large folios)
Date: Tue, 28 Jun 2022 16:21:55 -0700 [thread overview]
Message-ID: <YruNE72sW4Aizq8U@magnolia> (raw)
In-Reply-To: <20220628221757.GJ227878@dread.disaster.area>
On Wed, Jun 29, 2022 at 08:17:57AM +1000, Dave Chinner wrote:
> On Tue, Jun 28, 2022 at 02:18:24PM +0100, Matthew Wilcox wrote:
> > On Tue, Jun 28, 2022 at 12:31:55PM +0100, Matthew Wilcox wrote:
> > > On Tue, Jun 28, 2022 at 12:27:40PM +0100, Matthew Wilcox wrote:
> > > > On Tue, Jun 28, 2022 at 05:31:20PM +1000, Dave Chinner wrote:
> > > > > So using this technique, I've discovered that there's a dirty page
> > > > > accounting leak that eventually results in fsx hanging in
> > > > > balance_dirty_pages().
> > > >
> > > > Alas, I think this is only an accounting error, and not related to
> > > > the problem(s) that Darrick & Zorro are seeing. I think what you're
> > > > seeing is dirty pages being dropped at truncation without the
> > > > appropriate accounting. ie this should be the fix:
> > >
> > > Argh, try one that actually compiles.
> >
> > ... that one's going to underflow the accounting. Maybe I shouldn't
> > be writing code at 6am?
> >
> > diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> > index f7248002dad9..4eec6ee83e44 100644
> > --- a/mm/huge_memory.c
> > +++ b/mm/huge_memory.c
> > @@ -18,6 +18,7 @@
> > #include <linux/shrinker.h>
> > #include <linux/mm_inline.h>
> > #include <linux/swapops.h>
> > +#include <linux/backing-dev.h>
> > #include <linux/dax.h>
> > #include <linux/khugepaged.h>
> > #include <linux/freezer.h>
> > @@ -2439,11 +2440,15 @@ static void __split_huge_page(struct page *page, struct list_head *list,
> > __split_huge_page_tail(head, i, lruvec, list);
> > /* Some pages can be beyond EOF: drop them from page cache */
> > if (head[i].index >= end) {
> > - ClearPageDirty(head + i);
> > - __delete_from_page_cache(head + i, NULL);
> > + struct folio *tail = page_folio(head + i);
> > +
> > if (shmem_mapping(head->mapping))
> > shmem_uncharge(head->mapping->host, 1);
> > - put_page(head + i);
> > + else if (folio_test_clear_dirty(tail))
> > + folio_account_cleaned(tail,
> > + inode_to_wb(folio->mapping->host));
> > + __filemap_remove_folio(tail, NULL);
> > + folio_put(tail);
> > } else if (!PageAnon(page)) {
> > __xa_store(&head->mapping->i_pages, head[i].index,
> > head + i, 0);
> >
>
> Yup, that fixes the leak.
>
> Tested-by: Dave Chinner <dchinner@redhat.com>
Four hours of generic/522 running is long enough to conclude that this
is likely the fix for my problem and migrate long soak testing to my
main g/522 rig and:
Tested-by: Darrick J. Wong <djwong@kernel.org>
--D
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
next prev parent reply other threads:[~2022-06-28 23:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211216210715.3801857-1-willy@infradead.org>
[not found] ` <20211216210715.3801857-26-willy@infradead.org>
[not found] ` <YrO243DkbckLTfP7@magnolia>
[not found] ` <Yrku31ws6OCxRGSQ@magnolia>
[not found] ` <Yrm6YM2uS+qOoPcn@casper.infradead.org>
[not found] ` <YrosM1+yvMYliw2l@magnolia>
2022-06-28 7:31 ` Dave Chinner
2022-06-28 11:27 ` Matthew Wilcox
2022-06-28 11:31 ` Matthew Wilcox
2022-06-28 13:18 ` Matthew Wilcox
2022-06-28 20:57 ` Darrick J. Wong
2022-06-28 22:17 ` Dave Chinner
2022-06-28 23:21 ` Darrick J. Wong [this message]
2022-06-29 12:57 ` Brian Foster
2022-06-29 20:22 ` Darrick J. Wong
2022-07-01 16:03 ` Brian Foster
2022-07-01 18:03 ` Darrick J. Wong
2022-08-17 9:36 ` Dave Chinner
2022-08-17 23:53 ` Darrick J. Wong
2022-08-18 21:58 ` 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=YruNE72sW4Aizq8U@magnolia \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--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