From: kaixuxia <xiakaixu1987@gmail.com>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org, darrick.wong@oracle.com,
Kaixu Xia <kaixuxia@tencent.com>
Subject: Re: [PATCH] xfs: check if reserved free disk blocks is needed
Date: Tue, 7 Apr 2020 09:30:26 +0800 [thread overview]
Message-ID: <5f323870-6fcf-8935-fea6-bf0fa14d5c2e@gmail.com> (raw)
In-Reply-To: <20200406133859.GB20708@bfoster>
On 2020/4/6 21:38, Brian Foster wrote:
> On Sun, Apr 05, 2020 at 05:17:19PM +0800, xiakaixu1987@gmail.com wrote:
>> From: Kaixu Xia <kaixuxia@tencent.com>
>>
>> We don't need to create the new quota inodes from disk when
>> they exist already, so add check if reserved free disk blocks
>> is needed in xfs_trans_alloc().
>>
>
> I find the commit log to be a bit misleading. We don't actually get into
> this code if the inodes exist already. The need_alloc == false case
> looks like it has more to do with the scenario with the project/group
> inode is shared on older superblocks (explained in the comment near the
> top of the alloc function).
>
> That aside, the code looks fine to me, so with an improved commit log:
>
> Reviewed-by: Brian Foster <bfoster@redhat.com>
>
Thanks for your comments, will send the new version with the improved
commit log and add your Reviewed-by.
>> Signed-off-by: Kaixu Xia <kaixuxia@tencent.com>
>> ---
>> fs/xfs/xfs_qm.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/xfs/xfs_qm.c b/fs/xfs/xfs_qm.c
>> index 6678baa..b684b04 100644
>> --- a/fs/xfs/xfs_qm.c
>> +++ b/fs/xfs/xfs_qm.c
>> @@ -780,7 +780,8 @@ struct xfs_qm_isolate {
>> }
>>
>> error = xfs_trans_alloc(mp, &M_RES(mp)->tr_create,
>> - XFS_QM_QINOCREATE_SPACE_RES(mp), 0, 0, &tp);
>> + need_alloc ? XFS_QM_QINOCREATE_SPACE_RES(mp) : 0,
>> + 0, 0, &tp);
>> if (error)
>> return error;
>>
>> --
>> 1.8.3.1
>>
>
--
kaixuxia
prev parent reply other threads:[~2020-04-07 1:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 9:17 [PATCH] xfs: check if reserved free disk blocks is needed xiakaixu1987
2020-04-06 13:38 ` Brian Foster
2020-04-07 1:30 ` kaixuxia [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=5f323870-6fcf-8935-fea6-bf0fa14d5c2e@gmail.com \
--to=xiakaixu1987@gmail.com \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=kaixuxia@tencent.com \
--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