From: Greg KH <greg@kroah.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Leah Rumancik <leah.rumancik@gmail.com>,
stable@vger.kernel.org, Zhang Yi <yi.zhang@huawei.com>
Subject: Re: [PATCH for 5.4 1/3] ext4: check for out-of-order index extents in ext4_valid_extent_entries()
Date: Sun, 20 Feb 2022 15:51:08 +0100 [thread overview]
Message-ID: <YhJVXB1BeA1Dw045@kroah.com> (raw)
In-Reply-To: <Yg/6IgszAcONwk0n@mit.edu>
On Fri, Feb 18, 2022 at 02:57:22PM -0500, Theodore Ts'o wrote:
> Leah, thanks for doing the backport to 5.4! And Greg, thanks for queuing them up.
>
> I note that if we first cherry pick into 4.19.y a fix from 5.2 that
> probably should have been cc'ed to stable to begin with:
>
> 0a944e8a6c66 ("ext4: don't perform block validity checks on the journal inode")
This commit is already in the following releases:
3.16.85 4.4.221 4.4.263 4.9.221 4.9.263 4.14.178 4.14.227 4.19.73 4.19.182 5.2 5.7.18 5.8.4
> Leah's three backports to 5.4 will then apply to 4.19 LTS; I've run
> regression tests with the cherry-pick of 0a944e8a6c66 and Leah's three
> backports applied to 4.19.230, and the resulting kernel looks fine and
> prevents a kernel crash when running ext4/054.
>
> Greg, would you prefer that I send the patches for 4.19.y, or do you
> have what you need to do the cherry pick (all of the cherry picks are
> clean, and didn't require any manual resolution)?
The second commit does not apply cleanly, so I would need working
backported ones to get this right. I have queued up the first one now
already.
thanks,
greg k-h
prev parent reply other threads:[~2022-02-20 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 22:59 [PATCH for 5.4 1/3] ext4: check for out-of-order index extents in ext4_valid_extent_entries() Leah Rumancik
2022-02-17 22:59 ` [PATCH for 5.4 2/3] ext4: check for inconsistent extents between index and leaf block Leah Rumancik
2022-02-17 22:59 ` [PATCH for 5.4 3/3] ext4: prevent partial update of the extent blocks Leah Rumancik
2022-02-18 9:21 ` [PATCH for 5.4 1/3] ext4: check for out-of-order index extents in ext4_valid_extent_entries() Greg KH
2022-02-18 19:57 ` Theodore Ts'o
2022-02-20 14:51 ` 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=YhJVXB1BeA1Dw045@kroah.com \
--to=greg@kroah.com \
--cc=leah.rumancik@gmail.com \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yi.zhang@huawei.com \
/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