From: zhanchengbin <zhanchengbin1@huawei.com>
To: Jan Kara <jack@suse.cz>
Cc: <tytso@mit.edu>, <jack@suse.com>, <linux-ext4@vger.kernel.org>,
<yi.zhang@huawei.com>, <linfeilong@huawei.com>,
<liuzhiqiang26@huawei.com>
Subject: Re: [PATCH v4 1/2] ext4: fix inode tree inconsistency caused by ENOMEM in ext4_split_extent_at
Date: Wed, 15 Feb 2023 16:51:23 +0800 [thread overview]
Message-ID: <a666524b-e811-c35e-3f2b-f2d63622f674@huawei.com> (raw)
In-Reply-To: <20230214114835.hpjr4zgofrcp7hyy@quack3>
On 2023/2/14 19:48, Jan Kara wrote:
> On Mon 13-02-23 12:05:21, zhanchengbin wrote:
>> If ENOMEM fails when the extent is splitting, we need to restore the length
>> of the split extent.
>> In the call stack of the ext4_split_extent_at function, only in
>> ext4_ext_create_new_leaf will it alloc memory and change the shape of the
>> extent tree,even if an ENOMEM is returned at this time, the extent tree is
>> still self-consistent, Just restore the split extent lens in the function
>> ext4_split_extent_at.
>>
>> ext4_split_extent_at
>> ext4_ext_insert_extent
>> ext4_ext_create_new_leaf
>> 1)ext4_ext_split
>> ext4_find_extent
>> 2)ext4_ext_grow_indepth
>> ext4_find_extent
>>
>> Signed-off-by: zhanchengbin <zhanchengbin1@huawei.com>
>> ---
>> fs/ext4/extents.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
>> index 9de1c9d1a13d..0f95e857089e 100644
>> --- a/fs/ext4/extents.c
>> +++ b/fs/ext4/extents.c
>> @@ -935,6 +935,7 @@ ext4_find_extent(struct inode *inode, ext4_lblk_t block,
>>
>> bh = read_extent_tree_block(inode, path[ppos].p_idx, --i, flags);
>> if (IS_ERR(bh)) {
>> + EXT4_ERROR_INODE(inode, "IO error reading extent block");
>
> Why have you added this? Usually we don't log any additional errors for IO
> errors because the storage layer already reports it... Furthermore this
> would potentialy panic the system / remount the fs RO which we also usually
> don't do in case of IO errors, only in case of FS corruption.
>
> Honza
Because failure of read_extent_tree_block indirectly leads to filesystem
inconsistency in ext4_split_extent_at, I want the filesystem to become
read-only after failure.
- bin.
>
>> ret = PTR_ERR(bh);
>> goto err;
>> }
>> @@ -3251,7 +3252,7 @@ static int ext4_split_extent_at(handle_t *handle,
>> ext4_ext_mark_unwritten(ex2);
>>
>> err = ext4_ext_insert_extent(handle, inode, ppath, &newex, flags);
>> - if (err != -ENOSPC && err != -EDQUOT)
>> + if (err != -ENOSPC && err != -EDQUOT && err != -ENOMEM)
>> goto out;
>>
>> if (EXT4_EXT_MAY_ZEROOUT & split_flag) {
>> --
>> 2.31.1
>>
next prev parent reply other threads:[~2023-02-15 8:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 4:05 [PATCH v4 0/2] fix extents need to be restored when ext4_ext_insert_extent failed zhanchengbin
2023-02-13 4:05 ` [PATCH v4 1/2] ext4: fix inode tree inconsistency caused by ENOMEM in ext4_split_extent_at zhanchengbin
2023-02-14 11:48 ` Jan Kara
2023-02-15 8:51 ` zhanchengbin [this message]
2023-02-16 13:07 ` Jan Kara
2023-02-19 3:35 ` Theodore Ts'o
2023-02-13 4:05 ` [PATCH v4 2/2] ext4: clear the verified flag of the modified leaf or idx if error zhanchengbin
2023-02-13 6:18 ` kernel test robot
2023-02-13 6:19 ` kernel test robot
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=a666524b-e811-c35e-3f2b-f2d63622f674@huawei.com \
--to=zhanchengbin1@huawei.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linfeilong@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--cc=tytso@mit.edu \
--cc=yi.zhang@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