From: "Darrick J. Wong" <djwong@kernel.org>
To: Xiaole He <hexiaole1994@126.com>
Cc: linux-xfs@vger.kernel.org, hexiaole <hexiaole@kylinos.cn>
Subject: Re: Re: [PATCH v2] libxfs: fix inode reservation space for removing transaction
Date: Wed, 17 Aug 2022 10:22:05 -0700 [thread overview]
Message-ID: <Yv0jvckQV7EcE1Mt@magnolia> (raw)
In-Reply-To: <afd9ebb.1f54.182aa83c998.Coremail.hexiaole1994@126.com>
On Wed, Aug 17, 2022 at 02:35:39PM +0800, Xiaole He wrote:
> Yes, Darrick, I already see the patch been merged into the kernel
> source 'xfs-linux', thanks, but not see it in the userspace utilities
> source 'xfsprogs-dev', so I resend this patch again for the userspace
> utilities source 'xfsprogs-dev'.
>
> Is this action of resend neccesary? Sorry I do not know what is
> workflow of the 'libxfs' between the kernel source 'xfs-linux' and the
> userspace utilities souce 'xfsprogs-dev', is the patch of 'libxfs'
> will be merged into userspace utilities source 'xfsprogs-dev'
> automatically because it had been merged into the kernel source
> 'xfs-linux'? If so, I'm sorry for bother you and please ignore this
> mail.
Ah, sorry, I missed that. The xfsprogs maintainer automatically pulls
kernel libxfs changes into xfsprogs before the (xfsprogs) 6.0.0-rc1
release. It isn't usually necessary to submit a straight port, unless
you've tried porting it to userspace yourself and discovered that there
are other non-trivial changes needed.
--D
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> At 2022-08-16 23:23:41, "Darrick J. Wong" <djwong@kernel.org> wrote:
> >On Mon, Aug 15, 2022 at 10:54:58AM +0800, Xiaole He wrote:
> >> From: hexiaole <hexiaole@kylinos.cn>
> >>
> >> In 'libxfs/xfs_trans_resv.c', the comment for transaction of removing a
> >> directory entry mentions that there has 2 inode size of space to be
> >> reserverd, but the actual code only count for 1 inode size:
> >
> >Already merged, see 6.0-rc1.
> >
> >--D
> >
> >>
> >> /* libxfs/xfs_trans_resv.c begin */
> >> /*
> >> * For removing a directory entry we can modify:
> >> * the parent directory inode: inode size
> >> * the removed inode: inode size
> >> ...
> >> xfs_calc_remove_reservation(
> >> struct xfs_mount *mp)
> >> {
> >> return XFS_DQUOT_LOGRES(mp) +
> >> xfs_calc_iunlink_add_reservation(mp) +
> >> max((xfs_calc_inode_res(mp, 1) +
> >> ...
> >> /* libxfs/xfs_trans_resv.c end */
> >>
> >> Here only count for 1 inode size to be reserved in
> >> 'xfs_calc_inode_res(mp, 1)', rather than 2.
> >>
> >> Signed-off-by: hexiaole <hexiaole@kylinos.cn>
> >> ---
> >> V1 -> V2: djwong: remove redundant code citations
> >>
> >> libxfs/xfs_trans_resv.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/libxfs/xfs_trans_resv.c b/libxfs/xfs_trans_resv.c
> >> index d4a9f69e..797176d7 100644
> >> --- a/libxfs/xfs_trans_resv.c
> >> +++ b/libxfs/xfs_trans_resv.c
> >> @@ -514,7 +514,7 @@ xfs_calc_remove_reservation(
> >> {
> >> return XFS_DQUOT_LOGRES(mp) +
> >> xfs_calc_iunlink_add_reservation(mp) +
> >> - max((xfs_calc_inode_res(mp, 1) +
> >> + max((xfs_calc_inode_res(mp, 2) +
> >> xfs_calc_buf_res(XFS_DIROP_LOG_COUNT(mp),
> >> XFS_FSB_TO_B(mp, 1))),
> >> (xfs_calc_buf_res(4, mp->m_sb.sb_sectsize) +
> >> --
> >> 2.27.0
> >>
prev parent reply other threads:[~2022-08-17 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 2:54 [PATCH v2] libxfs: fix inode reservation space for removing transaction Xiaole He
2022-08-16 15:23 ` Darrick J. Wong
[not found] ` <afd9ebb.1f54.182aa83c998.Coremail.hexiaole1994@126.com>
2022-08-17 17:22 ` 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=Yv0jvckQV7EcE1Mt@magnolia \
--to=djwong@kernel.org \
--cc=hexiaole1994@126.com \
--cc=hexiaole@kylinos.cn \
--cc=linux-xfs@vger.kernel.org \
/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