public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Zhang Yi <yi.zhang@huaweicloud.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu,
	adilger.kernel@dilger.ca, jack@suse.cz, yi.zhang@huawei.com,
	chengzhihao1@huawei.com, yukuai3@huawei.com
Subject: Re: [PATCH v3 5/6] ext4: make ext4_map_blocks() distinguish delalloc only extent
Date: Fri, 5 Jan 2024 11:18:23 +0100	[thread overview]
Message-ID: <20240105101823.h5ucbtlhinghhbuk@quack3> (raw)
In-Reply-To: <20240105033018.1665752-6-yi.zhang@huaweicloud.com>

On Fri 05-01-24 11:30:17, Zhang Yi wrote:
> From: Zhang Yi <yi.zhang@huawei.com>
> 
> Add a new map flag EXT4_MAP_DELAYED to indicate the mapping range is a
> delayed allocated only (not unwritten) one, and making
> ext4_map_blocks() can distinguish it, no longer mixing it with holes.
> 
> Signed-off-by: Zhang Yi <yi.zhang@huawei.com>

Looks good. Feel free to add:

Reviewed-by: Jan Kara <jack@suse.cz>

								Honza

> ---
>  fs/ext4/ext4.h    | 4 +++-
>  fs/ext4/extents.c | 7 +++++--
>  fs/ext4/inode.c   | 2 ++
>  3 files changed, 10 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> index a5d784872303..55195909d32f 100644
> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
> @@ -252,8 +252,10 @@ struct ext4_allocation_request {
>  #define EXT4_MAP_MAPPED		BIT(BH_Mapped)
>  #define EXT4_MAP_UNWRITTEN	BIT(BH_Unwritten)
>  #define EXT4_MAP_BOUNDARY	BIT(BH_Boundary)
> +#define EXT4_MAP_DELAYED	BIT(BH_Delay)
>  #define EXT4_MAP_FLAGS		(EXT4_MAP_NEW | EXT4_MAP_MAPPED |\
> -				 EXT4_MAP_UNWRITTEN | EXT4_MAP_BOUNDARY)
> +				 EXT4_MAP_UNWRITTEN | EXT4_MAP_BOUNDARY |\
> +				 EXT4_MAP_DELAYED)
>  
>  struct ext4_map_blocks {
>  	ext4_fsblk_t m_pblk;
> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> index e0b7e48c4c67..6b64319a7df8 100644
> --- a/fs/ext4/extents.c
> +++ b/fs/ext4/extents.c
> @@ -4076,8 +4076,11 @@ static ext4_lblk_t ext4_ext_determine_insert_hole(struct inode *inode,
>  		/*
>  		 * The delalloc extent containing lblk, it must have been
>  		 * added after ext4_map_blocks() checked the extent status
> -		 * tree, adjust the length to the delalloc extent's after
> -		 * lblk.
> +		 * tree so we are not holding i_rwsem and delalloc info is
> +		 * only stabilized by i_data_sem we are going to release
> +		 * soon. Don't modify the extent status tree and report
> +		 * extent as a hole, just adjust the length to the delalloc
> +		 * extent's after lblk.
>  		 */
>  		len = es.es_lblk + es.es_len - lblk;
>  		return len;
> diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
> index 1b5e6409f958..c141bf6d8db2 100644
> --- a/fs/ext4/inode.c
> +++ b/fs/ext4/inode.c
> @@ -515,6 +515,8 @@ int ext4_map_blocks(handle_t *handle, struct inode *inode,
>  			map->m_len = retval;
>  		} else if (ext4_es_is_delayed(&es) || ext4_es_is_hole(&es)) {
>  			map->m_pblk = 0;
> +			map->m_flags |= ext4_es_is_delayed(&es) ?
> +					EXT4_MAP_DELAYED : 0;
>  			retval = es.es_len - (map->m_lblk - es.es_lblk);
>  			if (retval > map->m_len)
>  				retval = map->m_len;
> -- 
> 2.39.2
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

  reply	other threads:[~2024-01-05 10:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05  3:30 [PATCH v3 0/6] ext4: make ext4_map_blocks() recognize delalloc only extent Zhang Yi
2024-01-05  3:30 ` [PATCH v3 1/6] ext4: refactor ext4_da_map_blocks() Zhang Yi
2024-01-05  3:30 ` [PATCH v3 2/6] ext4: convert to exclusive lock while inserting delalloc extents Zhang Yi
2024-01-05  3:30 ` [PATCH v3 3/6] ext4: correct the hole length returned by ext4_map_blocks() Zhang Yi
2024-01-05 10:17   ` Jan Kara
2024-01-05 11:17     ` Zhang Yi
2024-01-05  3:30 ` [PATCH v3 4/6] ext4: add a hole extent entry in cache after punch Zhang Yi
2024-01-05  3:30 ` [PATCH v3 5/6] ext4: make ext4_map_blocks() distinguish delalloc only extent Zhang Yi
2024-01-05 10:18   ` Jan Kara [this message]
2024-01-05  3:30 ` [PATCH v3 6/6] ext4: make ext4_set_iomap() recognize IOMAP_DELALLOC map type Zhang Yi

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=20240105101823.h5ucbtlhinghhbuk@quack3 \
    --to=jack@suse.cz \
    --cc=adilger.kernel@dilger.ca \
    --cc=chengzhihao1@huawei.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=yi.zhang@huawei.com \
    --cc=yi.zhang@huaweicloud.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