public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Baokun Li <libaokun1@huawei.com>
To: <linux-ext4@vger.kernel.org>
Cc: <tytso@mit.edu>, <adilger.kernel@dilger.ca>, <jack@suse.cz>,
	<ritesh.list@gmail.com>, <linux-kernel@vger.kernel.org>,
	<yi.zhang@huawei.com>, <yangerkun@huawei.com>,
	<yukuai3@huawei.com>, <libaokun1@huawei.com>
Subject: [PATCH v3 0/8] ext4: fix WARNING in ext4_da_update_reserve_space
Date: Wed, 12 Apr 2023 20:41:18 +0800	[thread overview]
Message-ID: <20230412124126.2286716-1-libaokun1@huawei.com> (raw)

V1->V2:
	Modify the patch 1 description and add the Fixes tag.
	Add the patch 2 as suggested by Jan Kara.
V2->V3:
	Remove the redundant judgment of count in Patch [1].
	Rename ext4_es_alloc_should_nofail to ext4_es_must_keep.
	Split Patch [2].
	Make some functions return void to simplify the code.

This patch set consists of three parts:
1. Patch [1] fix WARNING in ext4_da_update_reserve_space.
2. Patch [2][3] fix extent tree inconsistencies that may be caused
   by memory allocation failures.
3. Patch [4]-[8] is cleanup.

Baokun Li (8):
  ext4: only update i_reserved_data_blocks on successful block
    allocation
  ext4: add a new helper to check if es must be kept
  ext4: use __GFP_NOFAIL if allocating extents_status cannot fail
  ext4: make __es_remove_extent return void
  ext4: make ext4_es_remove_extent return void
  ext4: make ext4_es_insert_delayed_block return void
  ext4: make ext4_es_insert_extent return void
  ext4: make ext4_zeroout_es return void

 fs/ext4/extents.c        |  49 ++++-----------
 fs/ext4/extents_status.c | 127 +++++++++++++++++----------------------
 fs/ext4/extents_status.h |  14 ++---
 fs/ext4/indirect.c       |   8 +++
 fs/ext4/inline.c         |  12 +---
 fs/ext4/inode.c          |  46 +++-----------
 6 files changed, 96 insertions(+), 160 deletions(-)

-- 
2.31.1


             reply	other threads:[~2023-04-12 12:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 12:41 Baokun Li [this message]
2023-04-12 12:41 ` [PATCH v3 1/8] ext4: only update i_reserved_data_blocks on successful block allocation Baokun Li
2023-04-12 18:45   ` Jan Kara
2023-04-12 12:41 ` [PATCH v3 2/8] ext4: add a new helper to check if es must be kept Baokun Li
2023-04-12 18:53   ` Jan Kara
2023-04-13  2:00     ` Baokun Li
2023-04-13 10:34       ` Jan Kara
2023-04-13 12:26         ` Baokun Li
2023-04-12 12:41 ` [PATCH v3 3/8] ext4: use __GFP_NOFAIL if allocating extents_status cannot fail Baokun Li
2023-04-13 10:30   ` Jan Kara
2023-04-24  3:45     ` Baokun Li
2023-04-12 12:41 ` [PATCH v3 4/8] ext4: make __es_remove_extent return void Baokun Li
2023-04-12 12:41 ` [PATCH v3 5/8] ext4: make ext4_es_remove_extent " Baokun Li
2023-04-12 12:41 ` [PATCH v3 6/8] ext4: make ext4_es_insert_delayed_block " Baokun Li
2023-04-12 14:19   ` kernel test robot
2023-04-13  2:36     ` Baokun Li
2023-04-12 17:24   ` kernel test robot
2023-04-12 12:41 ` [PATCH v3 7/8] ext4: make ext4_es_insert_extent " Baokun Li
2023-04-12 12:41 ` [PATCH v3 8/8] ext4: make ext4_zeroout_es " Baokun Li

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=20230412124126.2286716-1-libaokun1@huawei.com \
    --to=libaokun1@huawei.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ritesh.list@gmail.com \
    --cc=tytso@mit.edu \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai3@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