From: Kevin Fernandez <kevin@findhost.org>
To: Elliot Berman <elliotjb@elliotjb.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Sasha Levin <sashal@kernel.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Yongjian Sun <sunyongjian1@huawei.com>, Jan Kara <jack@suse.cz>,
stable@vger.kernel.org, regressions@lists.linux.dev,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
ntfs3@lists.linux.dev, Tom Bereknyei <tomberek@gmail.com>
Subject: Re: [PATCH 6.1.y 0/2] Fix NULL folio dereferences from IS_ERR() checks in 6.1.191
Date: Tue, 3 Nov 2026 01:42:07 +0000 [thread overview]
Message-ID: <auk775zR0FCl4L0X@hebergement-securise.com> (raw)
In-Reply-To: <20261102-ext4-ntfs3-null-folio-v1-0-4fd91ee23a4a@elliotjb.com>
I hit the same oops on 6.1.191 on my server (x86_64, via
ext4_release_file() -> filemap_flush()) and reproduced it in a VM with
write/sync/drop_caches.
Is the series needed on 6.1.y at all? When it was dropped from
6.1.167-rc1 for this same oops, Yongjian Sun noted that 6.1.y lacks
060913999d7a ("mm: migrate: support poisoned recover from migrate
folio"), which introduced the race fixed by bdc56a9c46b2:
https://lkml.iu.edu/hypermail/linux/kernel/2603.3/05097.html
If so, reverting might be simpler. The two folio conversions and three
prep commits are only in 6.1.191 as Stable-dep-of: bdc56a9c46b2, and
a8d83471c560 fixes one of them, so they could go with it. All seven
revert cleanly. In a QEMU test (minimal x86_64 config, same
reproducer): reverting a8d83471c560, a3a7d360252c, 862483175d3d and
d34e4fd4e73f avoids the oops, while reverting a3a7d360252c alone does
not (the oops is in the conversions); also reverting the prep commits
1c0f0e2b9b69, e6b6cbe9f2fb and e394adafb089 leaves
fs/ext4/mballoc.[ch] identical to v6.1.190.
next prev parent reply other threads:[~2026-11-03 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 14:37 Elliot Berman
2026-11-02 14:37 ` [PATCH 6.1.y 1/2] ext4: fix NULL folio dereference in mballoc Elliot Berman
2026-11-02 14:37 ` [PATCH 6.1.y 2/2] bs/ntfs3: fix NULL folio dereference in ntfs_lock_new_page() Elliot Berman
2026-11-02 17:22 ` [PATCH 6.1.y 0/2] Fix NULL folio dereferences from IS_ERR() checks in 6.1.191 Naman Jain
2026-11-03 1:42 ` Kevin Fernandez [this message]
2026-11-03 14:51 ` Sasha Levin
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=auk775zR0FCl4L0X@hebergement-securise.com \
--to=kevin@findhost.org \
--cc=adilger.kernel@dilger.ca \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=elliotjb@elliotjb.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sunyongjian1@huawei.com \
--cc=tomberek@gmail.com \
--cc=tytso@mit.edu \
--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
all inboxes | Powered by JetHome®