ext4: fix typos in mballoc

pa_plen -> pa_len
pa_start -> pa_pstart

Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
Reviewed-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
Link: https://lore.kernel.org/r/20230311170949.1047958-2-shikemeng@huaweicloud.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>

diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
index f09eb7f7fa5a9cfb6db2432757b6f1ebd7eeab67..0b03a3b90207120dbdf046022fbe89320adf4b4f 100644 (file)
--- a/fs/ext4/mballoc.c
+++ b/fs/ext4/mballoc.c
@@ -4146,7 +4146,7 @@ ext4_mb_normalize_request(struct ext4_allocation_context *ac,
         * provide gurantee on number of contiguous blocks allocation since that
         * depends upon free space left, etc).
         * In case of inode pa, later we use the allocated blocks
-        * [pa_start + fe_logical - pa_lstart, fe_len/size] from the preallocated
+        * [pa_pstart + fe_logical - pa_lstart, fe_len/size] from the preallocated
         * range of goal/best blocks [start, size] to put it at the
         * ac_o_ex.fe_logical extent of this inode.
         * (See ext4_mb_use_inode_pa() for more details)
@@ -4299,7 +4299,7 @@ static void ext4_mb_use_group_pa(struct ext4_allocation_context *ac,
        ac->ac_status = AC_STATUS_FOUND;
        ac->ac_pa = pa;
 
-       /* we don't correct pa_pstart or pa_plen here to avoid
+       /* we don't correct pa_pstart or pa_len here to avoid
         * possible race when the group is being loaded concurrently
         * instead we correct pa later, after blocks are marked
         * in on-disk bitmap -- see ext4_mb_release_context()