From: kaixuxia <xiakaixu1987@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org, Kaixu Xia <kaixuxia@tencent.com>
Subject: Re: [PATCH] xfs: simplify the flags setting in xfs_qm_scall_quotaon
Date: Sat, 11 Apr 2020 13:08:17 +0800 [thread overview]
Message-ID: <2092decb-7bbe-cd6c-4242-9f1ee532237b@gmail.com> (raw)
In-Reply-To: <20200411031838.GQ6742@magnolia>
On 2020/4/11 11:18, Darrick J. Wong wrote:
> On Sat, Apr 11, 2020 at 09:09:57AM +0800, kaixuxia wrote:
>>
>> On 2020/4/10 22:51, Darrick J. Wong wrote:
>>> On Fri, Apr 10, 2020 at 04:57:04PM +0800, xiakaixu1987@gmail.com wrote:
>>>> From: Kaixu Xia <kaixuxia@tencent.com>
>>>>
>>>> Simplify the setting of the flags value, and only consider
>>>> quota enforcement stuff here.
>>>>
>>>> Signed-off-by: Kaixu Xia <kaixuxia@tencent.com>
>>>> ---
>>>> fs/xfs/xfs_qm_syscalls.c | 6 +++---
>>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>>>
>>>> diff --git a/fs/xfs/xfs_qm_syscalls.c b/fs/xfs/xfs_qm_syscalls.c
>>>> index 5d5ac65..944486f 100644
>>>> --- a/fs/xfs/xfs_qm_syscalls.c
>>>> +++ b/fs/xfs/xfs_qm_syscalls.c
>>>> @@ -357,11 +357,11 @@
>>>
>>> No idea which function this is. diff -p, please.
>>
>> Yeah, the changed function is xfs_qm_scall_quotaon().
>> Anyway, the result of diff -p as follows,
>
> That was a request to generate your patches with diff -Naurp.
Got it, I will resend all the patches that have not been applied by
the xfs for-next branch with a single patchset.
>
> --D
>
>> *** fs/xfs/xfs_qm_syscalls.c Sat Apr 11 08:32:03 2020
>> --- /tmp/xfs_qm_syscalls.c Sat Apr 11 08:31:51 2020
>> *************** xfs_qm_scall_quotaon(
>> *** 357,367 ****
>> int error;
>> uint qf;
>>
>> /*
>> ! * Switching on quota accounting must be done at mount time,
>> ! * only consider quota enforcement stuff here.
>> */
>> ! flags &= XFS_ALL_QUOTA_ENFD;
>>
>> if (flags == 0) {
>> xfs_debug(mp, "%s: zero flags, m_qflags=%x",
>> --- 357,367 ----
>> int error;
>> uint qf;
>>
>> + flags &= (XFS_ALL_QUOTA_ACCT | XFS_ALL_QUOTA_ENFD);
>> /*
>> ! * Switching on quota accounting must be done at mount time.
>> */
>> ! flags &= ~(XFS_ALL_QUOTA_ACCT);
>>
>> if (flags == 0) {
>> xfs_debug(mp, "%s: zero flags, m_qflags=%x",
>>
>>>
>>> Also, please consider putting all these minor cleanups into a single
>>> patchset, it's a lot easier (for me) to track and land one series than
>>> it is to handle a steady trickle of single patches.
>> Yeah, got it. Should I resend all of the patches that have been
>> reviewed or just resend the last two patches with a single patchset?
>>
>> The patches that have been reviewed as follows,
>> xfs: trace quota allocations for all quota types
>> xfs: combine two if statements with same condition
>> xfs: check if reserved free disk blocks is needed
>> xfs: remove unnecessary variable udqp from xfs_ioctl_setattr
>>
>> The last two patches that have not been reviewed as follow,
>> xfs: remove unnecessary assertion from xfs_qm_vop_create_dqattach
>> xfs: simplify the flags setting in xfs_qm_scall_quotaon
>>
>>>
>>> --D
>>>
>>>> int error;
>>>> uint qf;
>>>>
>>>> - flags &= (XFS_ALL_QUOTA_ACCT | XFS_ALL_QUOTA_ENFD);
>>>> /*
>>>> - * Switching on quota accounting must be done at mount time.
>>>> + * Switching on quota accounting must be done at mount time,
>>>> + * only consider quota enforcement stuff here.
>>>> */
>>>> - flags &= ~(XFS_ALL_QUOTA_ACCT);
>>>> + flags &= XFS_ALL_QUOTA_ENFD;
>>>>
>>>> if (flags == 0) {
>>>> xfs_debug(mp, "%s: zero flags, m_qflags=%x",
>>>> --
>>>> 1.8.3.1
>>>>
>>
>> --
>> kaixuxia
--
kaixuxia
prev parent reply other threads:[~2020-04-11 5:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 8:57 [PATCH] xfs: simplify the flags setting in xfs_qm_scall_quotaon xiakaixu1987
2020-04-10 14:51 ` Darrick J. Wong
2020-04-11 1:09 ` kaixuxia
2020-04-11 3:18 ` Darrick J. Wong
2020-04-11 5:08 ` 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=2092decb-7bbe-cd6c-4242-9f1ee532237b@gmail.com \
--to=xiakaixu1987@gmail.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