From: Lukas Czerner <lczerner@redhat.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: "Ext4 Developers List" <linux-ext4@vger.kernel.org>,
"Nils Bars" <nils.bars@rub.de>,
"Moritz Schlögel" <moritz.schloegel@rub.de>,
"Nico Schiller" <nico.schiller@rub.de>
Subject: Re: [PATCH 5/7] e2fsck: avoid out-of-bounds write for very deep extent trees
Date: Tue, 7 Jun 2022 15:53:40 +0200 [thread overview]
Message-ID: <20220607135340.lv2k26ggillb2ixi@fedora> (raw)
In-Reply-To: <20220607042444.1798015-6-tytso@mit.edu>
On Tue, Jun 07, 2022 at 12:24:42AM -0400, Theodore Ts'o wrote:
> The kernel doesn't support extent trees deeper than 5
> (EXT4_MAX_EXTENT_DEPTH). For this reason we only maintain the extent
> tree statistics for 5 levels. Avoid out-of-bounds writes and reads if
> the extent tree is deeper than this.
>
> We keep these statistics to determine whether we should rebuild the
> extent tree. If the extent tree is too deep, we don't need the
> statistics because we should always rebuild the it.
Looks good.
Reviewed-by: Lukas Czerner <lczerner@redhat.com>
>
> Reported-by: Nils Bars <nils.bars@rub.de>
> Reported-by: Moritz Schlögel <moritz.schloegel@rub.de>
> Reported-by: Nico Schiller <nico.schiller@rub.de>
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> ---
> e2fsck/extents.c | 10 +++++++++-
> e2fsck/pass1.c | 3 ++-
> 2 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/e2fsck/extents.c b/e2fsck/extents.c
> index 01879f56..86fe00e7 100644
> --- a/e2fsck/extents.c
> +++ b/e2fsck/extents.c
> @@ -526,7 +526,8 @@ errcode_t e2fsck_check_rebuild_extents(e2fsck_t ctx, ext2_ino_t ino,
> */
> if (info.curr_entry == 1 &&
> !(extent.e_flags & EXT2_EXTENT_FLAGS_SECOND_VISIT) &&
> - !eti.force_rebuild) {
> + !eti.force_rebuild &&
> + info.curr_level < MAX_EXTENT_DEPTH_COUNT) {
> struct extent_tree_level *etl;
>
> etl = eti.ext_info + info.curr_level;
> @@ -580,6 +581,13 @@ errcode_t e2fsck_should_rebuild_extents(e2fsck_t ctx,
> extents_per_block = (ctx->fs->blocksize -
> sizeof(struct ext3_extent_header)) /
> sizeof(struct ext3_extent);
> +
> + /* If the extent tree is too deep, then rebuild it. */
> + if (info->max_depth > MAX_EXTENT_DEPTH_COUNT) {
> + pctx->blk = info->max_depth;
> + op = PR_1E_CAN_COLLAPSE_EXTENT_TREE;
> + goto rebuild;
> + }
> /*
> * If we can consolidate a level or shorten the tree, schedule the
> * extent tree to be rebuilt.
> diff --git a/e2fsck/pass1.c b/e2fsck/pass1.c
> index 11d7ce93..43972e7c 100644
> --- a/e2fsck/pass1.c
> +++ b/e2fsck/pass1.c
> @@ -2842,7 +2842,8 @@ static void scan_extent_node(e2fsck_t ctx, struct problem_context *pctx,
> if (pctx->errcode)
> return;
> if (!(ctx->options & E2F_OPT_FIXES_ONLY) &&
> - !pb->eti.force_rebuild) {
> + !pb->eti.force_rebuild &&
> + info.curr_level < MAX_EXTENT_DEPTH_COUNT) {
> struct extent_tree_level *etl;
>
> etl = pb->eti.ext_info + info.curr_level;
> --
> 2.31.0
>
next prev parent reply other threads:[~2022-06-07 13:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 4:24 [PATCH 0/7] Fix various bugs found via a fuzzing campaign Theodore Ts'o
2022-06-07 4:24 ` [PATCH 1/7] e2fsck: sanity check the journal inode number Theodore Ts'o
2022-06-07 13:12 ` Lukas Czerner
2022-06-07 4:24 ` [PATCH 2/7] e2fsck: fix potential out-of-bounds read in inc_ea_inode_refs() Theodore Ts'o
2022-06-07 13:30 ` Lukas Czerner
2022-06-07 4:24 ` [PATCH 3/7] libext2fs: add check for too-short directory blocks Theodore Ts'o
2022-06-07 13:31 ` Lukas Czerner
2022-06-07 4:24 ` [PATCH 4/7] e2fsck: check for xattr value size integer wraparound Theodore Ts'o
2022-06-07 13:33 ` Lukas Czerner
2022-06-07 4:24 ` [PATCH 5/7] e2fsck: avoid out-of-bounds write for very deep extent trees Theodore Ts'o
2022-06-07 13:53 ` Lukas Czerner [this message]
2022-06-07 4:24 ` [PATCH 6/7] libext2fs: check for cyclic loops in the extent tree Theodore Ts'o
2022-06-07 14:11 ` Lukas Czerner
2022-06-07 4:24 ` [PATCH 7/7] libext2fs: check for invalid blocks in ext2fs_punch_blocks() Theodore Ts'o
2022-06-07 14:22 ` Lukas Czerner
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=20220607135340.lv2k26ggillb2ixi@fedora \
--to=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=moritz.schloegel@rub.de \
--cc=nico.schiller@rub.de \
--cc=nils.bars@rub.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