From: Matthew Wilcox <willy@infradead.org>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-mm@kvack.org,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
linux-xfs@vger.kernel.org
Subject: Re: [REGRESSION] generic/127 failure caused by "mm: Use folio_next_pos()"
Date: Mon, 24 Nov 2025 19:20:16 +0000 [thread overview]
Message-ID: <aSSv8F_5QYHdqJaT@casper.infradead.org> (raw)
In-Reply-To: <20251124191811.GA26781@mac.lan>
On Mon, Nov 24, 2025 at 01:18:11PM -0600, Theodore Tso wrote:
> And then when I reverted commit 60a70e61430b, the test passed. I also
> checked and found that this commit was also causing generic/127 to
> fail for xfs:
>
> kvm-xfstests -c xfs/4k generic/127 --fail-loop-count 0 --kernel-build
>
> And, with the commit reverted the problem went away.
>
> The test logs for ext4 and xfs are attached. Willy, could you take a
> look? Many thanks!!
https://lore.kernel.org/linux-fsdevel/20251123220518.1447261-1-willy@infradead.org/
prev parent reply other threads:[~2025-11-24 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 19:18 Theodore Tso
2025-11-24 19:20 ` 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=aSSv8F_5QYHdqJaT@casper.infradead.org \
--to=willy@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
/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