From: Vlastimil Babka <vbabka@suse.cz>
To: Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: 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: Fri, 19 Apr 2024 09:51:35 +0200 [thread overview]
Message-ID: <3d4eac1f-8f33-4fbb-8c9f-5d7b2c50b6dd@suse.cz> (raw)
In-Reply-To: <ZiFt8uGMLIWuTh4g@casper.infradead.org>
On 4/18/24 9:01 PM, Matthew Wilcox wrote:
> 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.
It's a race and needs CONFIG_DEBUG_VM to be visible, which probably makes it
rare. What seems to be new are the stress tests that have more "luck" at
hitting it? Or maybe also the changes towards more high-order folio usage
make it more likely.
next prev parent reply other threads:[~2024-04-19 7:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 0:13 Luis Chamberlain
2024-04-18 1:39 ` Matthew Wilcox
2024-04-18 6:42 ` Luis Chamberlain
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
2024-04-19 7:51 ` Vlastimil Babka [this message]
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=3d4eac1f-8f33-4fbb-8c9f-5d7b2c50b6dd@suse.cz \
--to=vbabka@suse.cz \
--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=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