From: Lukas Czerner <lczerner@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: Ted Tso <tytso@mit.edu>,
linux-ext4@vger.kernel.org,
Ritesh Harjani <riteshh@linux.ibm.com>,
Wolfgang Frisch <wolfgang.frisch@suse.com>
Subject: Re: [PATCH 2/4] ext4: Don't allow overlapping system zones
Date: Tue, 21 Jul 2020 12:36:59 +0200 [thread overview]
Message-ID: <20200721103659.je33lyuqubuhkizg@work> (raw)
In-Reply-To: <20200715131812.7243-3-jack@suse.cz>
On Wed, Jul 15, 2020 at 03:18:10PM +0200, Jan Kara wrote:
> Currently, add_system_zone() just silently merges two added system zones
> that overlap. However the overlap should not happen and it generally
> suggests that some unrelated metadata overlap which indicates the fs is
> corrupted. We should have caught such problems earlier (e.g. in
> ext4_check_descriptors()) but add this check as another line of defense.
> In later patch we also use this for stricter checking of journal inode
> extent tree.
Looks good, thanks!
Reviewed-by: Lukas Czerner <lczerner@redhat.com>
>
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> fs/ext4/block_validity.c | 36 +++++++++++++-----------------------
> 1 file changed, 13 insertions(+), 23 deletions(-)
>
> diff --git a/fs/ext4/block_validity.c b/fs/ext4/block_validity.c
> index 16e9b2fda03a..b394a50ebbe3 100644
> --- a/fs/ext4/block_validity.c
> +++ b/fs/ext4/block_validity.c
> @@ -68,7 +68,7 @@ static int add_system_zone(struct ext4_system_blocks *system_blks,
> ext4_fsblk_t start_blk,
> unsigned int count)
> {
> - struct ext4_system_zone *new_entry = NULL, *entry;
> + struct ext4_system_zone *new_entry, *entry;
> struct rb_node **n = &system_blks->root.rb_node, *node;
> struct rb_node *parent = NULL, *new_node = NULL;
>
> @@ -79,30 +79,20 @@ static int add_system_zone(struct ext4_system_blocks *system_blks,
> n = &(*n)->rb_left;
> else if (start_blk >= (entry->start_blk + entry->count))
> n = &(*n)->rb_right;
> - else {
> - if (start_blk + count > (entry->start_blk +
> - entry->count))
> - entry->count = (start_blk + count -
> - entry->start_blk);
> - new_node = *n;
> - new_entry = rb_entry(new_node, struct ext4_system_zone,
> - node);
> - break;
> - }
> + else /* Unexpected overlap of system zones. */
> + return -EFSCORRUPTED;
> }
>
> - if (!new_entry) {
> - new_entry = kmem_cache_alloc(ext4_system_zone_cachep,
> - GFP_KERNEL);
> - if (!new_entry)
> - return -ENOMEM;
> - new_entry->start_blk = start_blk;
> - new_entry->count = count;
> - new_node = &new_entry->node;
> -
> - rb_link_node(new_node, parent, n);
> - rb_insert_color(new_node, &system_blks->root);
> - }
> + new_entry = kmem_cache_alloc(ext4_system_zone_cachep,
> + GFP_KERNEL);
> + if (!new_entry)
> + return -ENOMEM;
> + new_entry->start_blk = start_blk;
> + new_entry->count = count;
> + new_node = &new_entry->node;
> +
> + rb_link_node(new_node, parent, n);
> + rb_insert_color(new_node, &system_blks->root);
>
> /* Can we merge to the left? */
> node = rb_prev(new_node);
> --
> 2.16.4
>
next prev parent reply other threads:[~2020-07-21 10:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 13:18 [PATCH 0/4] ext4: Check journal inode extents more carefully Jan Kara
2020-07-15 13:18 ` [PATCH 1/4] ext4: Handle error of ext4_setup_system_zone() on remount Jan Kara
2020-07-21 10:36 ` Lukas Czerner
2020-07-27 11:02 ` Jan Kara
2020-07-27 11:22 ` Lukas Czerner
2020-07-15 13:18 ` [PATCH 2/4] ext4: Don't allow overlapping system zones Jan Kara
2020-07-21 10:36 ` Lukas Czerner [this message]
2020-07-15 13:18 ` [PATCH 3/4] ext4: Check journal inode extents more carefully Jan Kara
2020-07-21 10:38 ` Lukas Czerner
2020-07-27 10:59 ` Jan Kara
2020-07-15 13:18 ` [PATCH 4/4] ext4: Fold ext4_data_block_valid_rcu() into the caller Jan Kara
2020-07-21 10:39 ` 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=20200721103659.je33lyuqubuhkizg@work \
--to=lczerner@redhat.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=riteshh@linux.ibm.com \
--cc=tytso@mit.edu \
--cc=wolfgang.frisch@suse.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