From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Kemeng Shi <shikemeng@huaweicloud.com>,
tytso@mit.edu, adilger.kernel@dilger.ca, jack@suse.cz
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 04/21] ext4: get correct ext4_group_info in ext4_mb_prefetch_fini
Date: Fri, 17 Feb 2023 12:16:25 +0530 [thread overview]
Message-ID: <87ttzkiybi.fsf@doe.com> (raw)
In-Reply-To: <20230209194825.511043-5-shikemeng@huaweicloud.com>
Kemeng Shi <shikemeng@huaweicloud.com> writes:
> We always get ext4_group_desc with group + 1 and ext4_group_info with
> group to check if we need do initialize ext4_group_info for the group.
> Just get ext4_group_desc with group for ext4_group_info initialization
> check.
>
> Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
> ---
> fs/ext4/mballoc.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index 352ac9139fee..f24f80ecf318 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -2570,13 +2570,13 @@ void ext4_mb_prefetch_fini(struct super_block *sb, ext4_group_t group,
> unsigned int nr)
> {
> while (nr-- > 0) {
> - struct ext4_group_desc *gdp = ext4_get_group_desc(sb, group,
> - NULL);
> - struct ext4_group_info *grp = ext4_get_group_info(sb, group);
> + struct ext4_group_desc *gdp;
> + struct ext4_group_info *grp;
We can even declare these variables at the begining of the function like
in [1]. Also I would advise to rearrange any "fixes" patches at the
begining of the patch series and "cleanup" patches at the end.
e.g. this looks like a fix to me.
That way it is sometimes easier for people to cherry-pick any fixes if
required in their older kernel trees. ;)
[1]: https://lore.kernel.org/all/85bbcb3774e38de65b737ef0000241ddbdda73aa.1674822311.git.ojaswin@linux.ibm.com/
-ritesh
>
> if (!group)
> group = ext4_get_groups_count(sb);
> group--;
> + gdp = ext4_get_group_desc(sb, group, NULL);
> grp = ext4_get_group_info(sb, group);
>
> if (EXT4_MB_GRP_NEED_INIT(grp) &&
> --
> 2.30.0
next prev parent reply other threads:[~2023-02-17 6:46 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 19:48 [PATCH 00/21] Some bugfix and cleanup to mballoc Kemeng Shi
2023-02-09 19:48 ` [PATCH 01/21] ext4: set goal start correctly in ext4_mb_normalize_request Kemeng Shi
2023-02-13 6:56 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 02/21] ext4: allow to find by goal if EXT4_MB_HINT_GOAL_ONLY is set Kemeng Shi
2023-02-13 6:57 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 03/21] ext4: avoid to use preallocated blocks " Kemeng Shi
2023-02-13 8:38 ` Ojaswin Mujoo
2023-02-13 13:27 ` Kemeng Shi
2023-02-09 19:48 ` [PATCH 04/21] ext4: get correct ext4_group_info in ext4_mb_prefetch_fini Kemeng Shi
2023-02-13 7:03 ` Ojaswin Mujoo
2023-02-13 12:27 ` Kemeng Shi
2023-02-13 20:14 ` Ojaswin Mujoo
2023-02-14 1:12 ` Kemeng Shi
2023-02-17 6:46 ` Ritesh Harjani [this message]
2023-02-17 7:19 ` Kemeng Shi
2023-02-09 19:48 ` [PATCH 05/21] ext4: correct calculation of s_mb_preallocated Kemeng Shi
2023-02-13 7:04 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 06/21] ext4: correct start of used group pa for debug in ext4_mb_use_group_pa Kemeng Shi
2023-02-13 7:09 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 07/21] ext4: protect pa->pa_free in ext4_discard_allocated_blocks Kemeng Shi
2023-02-13 8:42 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 08/21] ext4: add missed brelse in ext4_free_blocks_simple Kemeng Shi
2023-02-13 19:46 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 09/21] ext4: remove unused return value of ext4_mb_try_best_found and ext4_mb_free_metadata Kemeng Shi
2023-02-13 19:47 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 10/21] ext4: Remove unnecessary release when memory allocation failed in ext4_mb_init_cache Kemeng Shi
2023-02-13 19:48 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 11/21] ext4: remove unnecessary e4b->bd_buddy_page check in ext4_mb_load_buddy_gfp Kemeng Shi
2023-02-13 19:48 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 12/21] ext4: remove unnecessary check in ext4_mb_new_blocks Kemeng Shi
2023-02-13 19:49 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 13/21] ext4: remove dead check in mb_buddy_mark_free Kemeng Shi
2023-02-13 19:50 ` Ojaswin Mujoo
2023-02-17 1:24 ` Kemeng Shi
2023-02-09 19:48 ` [PATCH 14/21] ext4: remove ac->ac_found > sbi->s_mb_min_to_scan dead check in ext4_mb_check_limits Kemeng Shi
2023-02-13 19:51 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 15/21] ext4: use best found when complex scan of group finishs Kemeng Shi
2023-02-13 19:53 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 16/21] ext4: remove unnecessary exit_meta_group_info tag Kemeng Shi
2023-02-13 19:54 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 17/21] ext4: remove unnecessary count2 in ext4_free_data_in_buddy Kemeng Shi
2023-02-13 19:56 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 18/21] ext4: remove unnecessary goto in ext4_mb_mark_diskspace_used Kemeng Shi
2023-02-13 19:58 ` Ojaswin Mujoo
2023-02-17 6:36 ` Ritesh Harjani
2023-02-09 19:48 ` [PATCH 19/21] ext4: remove repeat assignment to ac_f_ex Kemeng Shi
2023-02-13 20:10 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 20/21] ext4: remove comment code ext4_discard_preallocations Kemeng Shi
2023-02-13 20:11 ` Ojaswin Mujoo
2023-02-09 19:48 ` [PATCH 21/21] ext4: simplify calculation of blkoff in ext4_mb_new_blocks_simple Kemeng Shi
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=87ttzkiybi.fsf@doe.com \
--to=ritesh.list@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shikemeng@huaweicloud.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox