From: "Theodore Ts'o" <tytso@mit.edu>
To: Sasha Levin <sashal@kernel.org>
Cc: Mathieu Othacehe <othacehe@gnu.org>,
stable@vger.kernel.org, jack@suse.cz,
Marcus Hoffmann <marcus.hoffmann@othermo.de>,
famzah@icdsoft.com, gregkh@linuxfoundation.org,
anton.reding@landisgyr.com
Subject: Re: kernel BUG at fs/ext4/inode.c:1914 - page_buffers()
Date: Wed, 4 Oct 2023 23:54:33 -0400 [thread overview]
Message-ID: <20231005035433.GA6358@mit.edu> (raw)
In-Reply-To: <ZR06COwVo7bEfP/5@sashalap>
On Wed, Oct 04, 2023 at 06:10:16AM -0400, Sasha Levin wrote:
> On Wed, Oct 04, 2023 at 11:37:22AM +0200, Mathieu Othacehe wrote:
> >
> > bd159398a2d2 ("jdb2: Don't refuse invalidation of already invalidated buffers")
> > d84c9ebdac1e ("ext4: Mark pages with journalled data dirty")
> > 265e72efa99f ("ext4: Keep pages with journalled data dirty")
> > 5e1bdea6391d ("ext4: Clear dirty bit from pages without data to write")
> > 1f1a55f0bf06 ("ext4: Commit transaction before writing back pages in data=journal mode")
> > e360c6ed7274 ("ext4: Drop special handling of journalled data from ext4_sync_file()")
> > c000dfec7e88 ("ext4: Drop special handling of journalled data from extent shifting operations")
> > 783ae448b7a2 ("ext4: Fix special handling of journalled data from extent zeroing")
> > 56c2a0e3d90d ("ext4: Drop special handling of journalled data from ext4_evict_inode()")
> > 7c375870fdc5 ("ext4: Drop special handling of journalled data from ext4_quota_on()")
> > 951cafa6b80e ("ext4: Simplify handling of journalled data in ext4_bmap()")
> > ab382539adcb ("ext4: Update comment in mpage_prepare_extent_to_map()")
> > d0ab8368c175 ("Revert "ext4: Fix warnings when freezing filesystem with journaled data"")
> > 1077b2d53ef5 ("ext4: fix fsync for non-directories")
> >
> > Or apply the proposed, attached patch. Do you think that would be an
> > option?
>
> Backporting the series would be ideal. Is this only for the 5.15 kernel?
If we're going to backport all of these patches, I'd really would like
to see a full regression test run, using something like:
gce-xfstests ltm -c ext4/all -g auto
before and after applying all of these patches, to make sure there are
no regression.
(or you can "kvm-xfstests -c ext4/all -g auto" but be prepared for it
to take over 24 hours of run time. With gce-xfstesets we start a
dozen VM's in parallel so it finishes in about 2.5 hours. See
https://thunk.org/gce-xfstests for more information.)
If you someone who does the backports can send me a pointer to a git
branch, I can run the tests for you, if that would be helpful.
Thanks!!
- Ted
next prev parent reply other threads:[~2023-10-05 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 9:37 kernel BUG at fs/ext4/inode.c:1914 - page_buffers() Mathieu Othacehe
2023-10-04 10:10 ` Sasha Levin
2023-10-05 3:54 ` Theodore Ts'o [this message]
2023-10-05 7:08 ` Mathieu Othacehe
2023-10-06 9:15 ` Jan Kara
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=20231005035433.GA6358@mit.edu \
--to=tytso@mit.edu \
--cc=anton.reding@landisgyr.com \
--cc=famzah@icdsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=marcus.hoffmann@othermo.de \
--cc=othacehe@gnu.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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