From: Greg KH <gregkh@linuxfoundation.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 5.10 0/3] Fix kernel crash caused by ext4/054
Date: Wed, 22 Dec 2021 13:02:10 +0100 [thread overview]
Message-ID: <YcMTwuKA0k16TwwJ@kroah.com> (raw)
In-Reply-To: <20211220153659.2120506-1-tytso@mit.edu>
On Mon, Dec 20, 2021 at 10:36:56AM -0500, Theodore Ts'o wrote:
> The following commits were cherry-picked from upstream to fix a crash
> in ext4/054. There was a minor fix-up needed in the first patch,
> although no other changes were needed for the 2nd and 3rd patches.
>
> Ext4/054 will cause older LTS kernels to crash, but unfortunately
> these patches will need further back-porting to apply to 5.4, never
> mind older LTS kernels. But at least here are the fixes for 5.10....
>
> Zhang Yi (3):
> ext4: prevent partial update of the extent blocks
> ext4: check for out-of-order index extents in
> ext4_valid_extent_entries()
> ext4: check for inconsistent extents between index and leaf block
>
> fs/ext4/extents.c | 93 ++++++++++++++++++++++++++++++++---------------
> 1 file changed, 63 insertions(+), 30 deletions(-)
>
> --
> 2.31.0
>
I also had to apply them to 5.15.y as you do not want people to upgrade
and have a regression.
thanks,
greg k-h
prev parent reply other threads:[~2021-12-22 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 15:36 [PATCH 5.10 0/3] Fix kernel crash caused by ext4/054 Theodore Ts'o
2021-12-20 15:36 ` [PATCH 1/3] ext4: prevent partial update of the extent blocks Theodore Ts'o
2021-12-20 15:36 ` [PATCH 5.10 2/3] ext4: check for out-of-order index extents in ext4_valid_extent_entries() Theodore Ts'o
2021-12-20 15:36 ` [PATCH 5.10 3/3] ext4: check for inconsistent extents between index and leaf block Theodore Ts'o
2021-12-22 12:02 ` Greg KH [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=YcMTwuKA0k16TwwJ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.