From: Greg KH <gregkh@linuxfoundation.org>
To: Marcus Hoffmann <marcus.hoffmann@othermo.de>
Cc: tytso@mit.edu, famzah@icdsoft.com, jack@suse.cz,
linux-ext4@vger.kernel.org
Subject: Re: kernel BUG at fs/ext4/inode.c:1914 - page_buffers()
Date: Fri, 12 May 2023 21:19:11 +0900 [thread overview]
Message-ID: <2023051249-finalize-sneak-2864@gregkh> (raw)
In-Reply-To: <578c0eb1-5271-b5fe-afa2-e2c1107b8968@othermo.de>
On Thu, May 11, 2023 at 11:21:27AM +0200, Marcus Hoffmann wrote:
> Hi,
>
> > On Wed, Mar 15, 2023 at 18:57, Theodore Ts'o wrote:
> >
> > Yeah, sorry, I didn't see it since it was in an attachment as opposed
> > to with an explicit [PATCH] subject line.
> >
> > And at this point, the data=journal writeback patches have landed in
> > the ext4/dev tree, and while we could try to see if we could land this
> > before the next merge window, I'm worried about merge or semantic
> > conflicts of having both patches in a tree at one time.
> >
> > I guess we could send it to Linus, let it get backported into stable,
> > and then revert it during the merge window, ahead of applying the
> > data=journal cleanup patch series. But that seems a bit ugly. Or we
> > could ask for an exception from the stable kernel folks, after I do a
> > full set of xfstests runs on it. (Of course, I don't think anyone has
> > been able to create a reliable reproducer, so all we can do is to test
> > for regression failures.)
> >
> > Jan, Greg, what do you think?
>
> We've noticed this appearing for us as well now (on 5.15 with
> data=journaled) and I wanted to ask what the status here is. Did any fix
> here make it into a stable kernel yet? If not, I suppose I can still
> apply the patch posted above as a quick-fix until this (or another
> solution) makes it into the stable tree?
Any reason you can't just move to 6.1.y instead? What prevents that?
thanks,
greg k-h
next prev parent reply other threads:[~2023-05-12 12:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 14:48 kernel BUG at fs/ext4/inode.c:1914 - page_buffers() Ivan Zahariev
2022-12-05 17:27 ` Ivan Zahariev
2022-12-05 21:10 ` Theodore Ts'o
2022-12-05 21:50 ` Ivan Zahariev
2023-01-12 15:07 ` Jan Kara
2023-03-15 11:27 ` Ivan Zahariev
2023-03-15 17:32 ` Jan Kara
2023-03-15 18:57 ` Theodore Ts'o
2023-05-11 9:21 ` Marcus Hoffmann
2023-05-12 12:19 ` Greg KH [this message]
2023-05-12 14:24 ` Marcus Hoffmann
2023-05-12 22:50 ` Greg KH
2023-05-15 9:10 ` Jan Kara
2023-09-20 9:40 ` Mathieu Othacehe
2023-09-22 9:54 ` 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=2023051249-finalize-sneak-2864@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=famzah@icdsoft.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=marcus.hoffmann@othermo.de \
--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;
as well as URLs for NNTP newsgroup(s).