[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231221150558.2740823-1-libaokun1@huawei.com>
Date: Thu, 21 Dec 2023 23:05:50 +0800
From: Baokun Li <libaokun1@...wei.com>
To: <linux-ext4@...r.kernel.org>
CC: <tytso@....edu>, <adilger.kernel@...ger.ca>, <jack@...e.cz>,
<ritesh.list@...il.com>, <linux-kernel@...r.kernel.org>,
<yi.zhang@...wei.com>, <yangerkun@...wei.com>, <yukuai3@...wei.com>,
<libaokun1@...wei.com>
Subject: [PATCH v2 0/8] ext4: fix divide error in mb_update_avg_fragment_size()
V1->V2:
Fixed some things pointed out by Jan Kara.
Fixed more cases where blocks could be allocated from corrupted groups.
[V1]: https://lore.kernel.org/all/20231218141814.1477338-1-libaokun1@huawei.com/
Baokun Li (8):
ext4: fix double-free of blocks due to wrong extents moved_len
ext4: do not trim the group with corrupted block bitmap
ext4: regenerate buddy after block freeing failed if under fc replay
ext4: avoid bb_free and bb_fragments inconsistency in mb_free_blocks()
ext4: avoid dividing by 0 in mb_update_avg_fragment_size() when block
bitmap corrupt
ext4: avoid allocating blocks from corrupted group in
ext4_mb_try_best_found()
ext4: avoid allocating blocks from corrupted group in
ext4_mb_find_by_goal()
ext4: mark the group block bitmap as corrupted before reporting an
error
fs/ext4/mballoc.c | 76 +++++++++++++++++++++++++++++--------------
fs/ext4/move_extent.c | 6 ++--
2 files changed, 53 insertions(+), 29 deletions(-)
--
2.31.1
Powered by blists - more mailing lists