From: Greg KH <gregkh@linuxfoundation.org>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: stable@vger.kernel.org, tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
joneslee@google.com
Subject: Re: [PATCH][for stable 5.{15, 10} 0/4] ext4: Fix kernel BUG in ext4_free_blocks
Date: Wed, 15 Mar 2023 09:17:34 +0100 [thread overview]
Message-ID: <ZBF/HpuRkBVQxcrp@kroah.com> (raw)
In-Reply-To: <20230302153610.1204653-1-tudor.ambarus@linaro.org>
On Thu, Mar 02, 2023 at 03:36:06PM +0000, Tudor Ambarus wrote:
> Hi,
>
> This patch set is intended for stable/linux-5.{15, 10}.y. The patches
> applied cleanly without deviations from the original upstream patches.
> The last patch is fixing the bug reported at [1]. The other three are
> prerequisites for the last commit. I tested the patches and I confirm
> that the reproducer no longer complains on linux-5.{15, 10}.y. Older
> LTS kernels have more dependencies, let's fix these until I sort out
> what else should be backported for the older LTS kernels.
>
> [1] LINK: https://syzkaller.appspot.com/bug?id=5266d464285a03cee9dbfda7d2452a72c3c2ae7c
>
> Cheers,
> ta
>
> Lukas Czerner (1):
> ext4: block range must be validated before use in ext4_mb_clear_bb()
>
> Ritesh Harjani (3):
> ext4: refactor ext4_free_blocks() to pull out ext4_mb_clear_bb()
> ext4: add ext4_sb_block_valid() refactored out of
> ext4_inode_block_valid()
> ext4: add strict range checks while freeing blocks
>
> fs/ext4/block_validity.c | 26 +++--
> fs/ext4/ext4.h | 3 +
> fs/ext4/mballoc.c | 205 +++++++++++++++++++++++----------------
> 3 files changed, 139 insertions(+), 95 deletions(-)
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-03-15 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 15:36 [PATCH][for stable 5.{15, 10} 0/4] ext4: Fix kernel BUG in ext4_free_blocks Tudor Ambarus
2023-03-02 15:36 ` [PATCH][for stable 5.{15, 10} 1/4] ext4: refactor ext4_free_blocks() to pull out ext4_mb_clear_bb() Tudor Ambarus
2023-03-02 15:36 ` [PATCH][for stable 5.{15, 10} 2/4] ext4: add ext4_sb_block_valid() refactored out of ext4_inode_block_valid() Tudor Ambarus
2023-03-02 15:36 ` [PATCH][for stable 5.{15, 10} 3/4] ext4: add strict range checks while freeing blocks Tudor Ambarus
2023-03-02 15:36 ` [PATCH][for stable 5.{15, 10} 4/4] ext4: block range must be validated before use in ext4_mb_clear_bb() Tudor Ambarus
2023-03-15 8:17 ` 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=ZBF/HpuRkBVQxcrp@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adilger.kernel@dilger.ca \
--cc=joneslee@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tudor.ambarus@linaro.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 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).