All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Yan <yanaijie@huawei.com>
To: Guoqing Jiang <guoqing.jiang@linux.dev>, <tytso@mit.edu>,
	<adilger.kernel@dilger.ca>
Cc: <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: make ext4_mb_initialize_context return void
Date: Thu, 27 Oct 2022 14:29:34 +0800	[thread overview]
Message-ID: <bf9dba6f-50c6-5ba8-31e3-b60de18105f1@huawei.com> (raw)
In-Reply-To: <20221027032435.27374-1-guoqing.jiang@linux.dev>


On 2022/10/27 11:24, Guoqing Jiang wrote:
> Change the return type to void since it always return 0, and no need
> to do the checking in ext4_mb_new_blocks.
> 
> Signed-off-by: Guoqing Jiang <guoqing.jiang@linux.dev>
> ---
>   fs/ext4/mballoc.c | 10 ++--------
>   1 file changed, 2 insertions(+), 8 deletions(-)
> 
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index 9dad93059945..5b2ae37a8b80 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -5204,7 +5204,7 @@ static void ext4_mb_group_or_file(struct ext4_allocation_context *ac)
>   	mutex_lock(&ac->ac_lg->lg_mutex);
>   }
>   
> -static noinline_for_stack int
> +static noinline_for_stack void
>   ext4_mb_initialize_context(struct ext4_allocation_context *ac,
>   				struct ext4_allocation_request *ar)
>   {
> @@ -5253,8 +5253,6 @@ ext4_mb_initialize_context(struct ext4_allocation_context *ac,
>   			(unsigned) ar->lleft, (unsigned) ar->pleft,
>   			(unsigned) ar->lright, (unsigned) ar->pright,
>   			inode_is_open_for_write(ar->inode) ? "" : "non-");
> -	return 0;
> -
>   }
>   
>   static noinline_for_stack void
> @@ -5591,11 +5589,7 @@ ext4_fsblk_t ext4_mb_new_blocks(handle_t *handle,
>   		goto out;
>   	}
>   
> -	*errp = ext4_mb_initialize_context(ac, ar);
> -	if (*errp) {
> -		ar->len = 0;
> -		goto out;
> -	}
> +	ext4_mb_initialize_context(ac, ar);

This changed the logic here slightly. *errp will not be intialized with 
zero after this change. So we need to carefully check whether this will 
cause any issues.

Thanks,
Jason

>   
>   	ac->ac_op = EXT4_MB_HISTORY_PREALLOC;
>   	seq = this_cpu_read(discard_pa_seq);
> 

  reply	other threads:[~2022-10-27  6:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27  3:24 [PATCH] ext4: make ext4_mb_initialize_context return void Guoqing Jiang
2022-10-27  6:29 ` Jason Yan [this message]
2022-10-27  8:12   ` Guoqing Jiang
2022-10-28 10:54     ` Ojaswin Mujoo
2022-10-29  2:56       ` Guoqing Jiang

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=bf9dba6f-50c6-5ba8-31e3-b60de18105f1@huawei.com \
    --to=yanaijie@huawei.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=guoqing.jiang@linux.dev \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.