From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Christoph Hellwig <hch@infradead.org>,
Luis Chamberlain <mcgrof@kernel.org>,
fstests@vger.kernel.org, kdevops@lists.linux.dev,
linux-xfs@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, david@redhat.com,
linmiaohe@huawei.com, muchun.song@linux.dev, osalvador@suse.de
Subject: Re: [PATCH] fstests: add fsstress + compaction test
Date: Thu, 18 Apr 2024 20:01:06 +0100 [thread overview]
Message-ID: <ZiFt8uGMLIWuTh4g@casper.infradead.org> (raw)
In-Reply-To: <20240418114552.37e9cc827d68e3c4781dd61a@linux-foundation.org>
On Thu, Apr 18, 2024 at 11:45:52AM -0700, Andrew Morton wrote:
> It indeed appears that I can move
>
> mm-create-folio_flag_false-and-folio_type_ops-macros.patch
> mm-support-page_mapcount-on-page_has_type-pages.patch
> mm-turn-folio_test_hugetlb-into-a-pagetype.patch
> mm-turn-folio_test_hugetlb-into-a-pagetype-fix.patch
>
> without merge or build issues. I added
>
> Fixes: 9c5ccf2db04b ("mm: remove HUGETLB_PAGE_DTOR")
> Cc: <stable@vger.kernel.org>
>
> to all patches.
>
> But a question: 9c5ccf2db04b is from August 2023. Why are we seeing
> this issue now?
We saw it earlier, we just didn't know how to fix it.
eg December 2023:
https://lore.kernel.org/all/ZXNhGsX32y19a2Xv@casper.infradead.org/
I think there were earlier reports, but I'm not finding them now.
next prev parent reply other threads:[~2024-04-18 19:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 0:13 [PATCH] fstests: add fsstress + compaction test Luis Chamberlain
2024-04-18 1:39 ` Matthew Wilcox
2024-04-18 6:42 ` Luis Chamberlain
2024-04-18 13:30 ` Matthew Wilcox
2024-04-18 6:57 ` Christoph Hellwig
2024-04-18 9:19 ` Vlastimil Babka
2024-04-18 18:45 ` Andrew Morton
2024-04-18 19:01 ` Matthew Wilcox [this message]
2024-04-19 7:51 ` Vlastimil Babka
2024-04-19 17:25 ` Luis Chamberlain
2024-04-20 14:02 ` Zorro Lang
2024-05-28 22:58 ` Luis Chamberlain
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=ZiFt8uGMLIWuTh4g@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=kdevops@lists.linux.dev \
--cc=linmiaohe@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=vbabka@suse.cz \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).