From: "Darrick J. Wong" <djwong@kernel.org>
To: Stephen Zhang <starzhangzsd@gmail.com>
Cc: dchinner@redhat.com, chandan.babu@oracle.com,
yang.guang5@zte.com.cn, zhangshida@kylinos.cn,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] xfs: trim the mapp array accordingly in xfs_da_grow_inode_int
Date: Tue, 20 Sep 2022 17:48:41 -0700 [thread overview]
Message-ID: <YypfaXzd3usW6b5i@magnolia> (raw)
In-Reply-To: <20220918064808.1206441-1-zhangshida@kylinos.cn>
On Sun, Sep 18, 2022 at 02:48:08PM +0800, Stephen Zhang wrote:
> Take a look at the for-loop in xfs_da_grow_inode_int:
> ======
> for(){
> nmap = min(XFS_BMAP_MAX_NMAP, count);
> ...
> error = xfs_bmapi_write(...,&mapp[mapi], &nmap);//(..., $1, $2)
> ...
> mapi += nmap;
> }
> =====
> where $1 stands for the start address of the array,
> while $2 is used to indicate the size of the array.
>
> The array $1 will advance by $nmap in each iteration after
> the allocation of extents.
> But the size $2 still remains unchanged, which is determined by
> min(XFS_BMAP_MAX_NMAP, count).
>
> It seems that it has forgotten to trim the mapp array after each
> iteration, so change it.
>
> Signed-off-by: Shida Zhang <zhangshida@kylinos.cn>
I think this look correct...
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> Changes from v1:
> - Using the current calculation to calculate the remaining number of
> blocks is enough, as suggested by Dave.
> ---
> fs/xfs/libxfs/xfs_da_btree.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/xfs/libxfs/xfs_da_btree.c b/fs/xfs/libxfs/xfs_da_btree.c
> index e7201dc68f43..e576560b46e9 100644
> --- a/fs/xfs/libxfs/xfs_da_btree.c
> +++ b/fs/xfs/libxfs/xfs_da_btree.c
> @@ -2192,8 +2192,8 @@ xfs_da_grow_inode_int(
> */
> mapp = kmem_alloc(sizeof(*mapp) * count, 0);
> for (b = *bno, mapi = 0; b < *bno + count; ) {
> - nmap = min(XFS_BMAP_MAX_NMAP, count);
> c = (int)(*bno + count - b);
> + nmap = min(XFS_BMAP_MAX_NMAP, c);
> error = xfs_bmapi_write(tp, dp, b, c,
> xfs_bmapi_aflag(w)|XFS_BMAPI_METADATA,
> args->total, &mapp[mapi], &nmap);
> --
> 2.27.0
>
prev parent reply other threads:[~2022-09-21 0:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 6:48 [PATCH v2] xfs: trim the mapp array accordingly in xfs_da_grow_inode_int Stephen Zhang
2022-09-21 0:48 ` Darrick J. Wong [this message]
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=YypfaXzd3usW6b5i@magnolia \
--to=djwong@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=dchinner@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=starzhangzsd@gmail.com \
--cc=yang.guang5@zte.com.cn \
--cc=zhangshida@kylinos.cn \
/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.