From: xiakaixu1987@gmail.com
To: linux-xfs@vger.kernel.org
Cc: darrick.wong@oracle.com, Kaixu Xia <kaixuxia@tencent.com>
Subject: [PATCH v5 0/3] xfs: random fixes for disk quota
Date: Sat, 10 Oct 2020 10:54:18 +0800 [thread overview]
Message-ID: <1602298461-32576-1-git-send-email-kaixuxia@tencent.com> (raw)
From: Kaixu Xia <kaixuxia@tencent.com>
Hi all,
This patchset include random fixes and code cleanups for disk quota.
In order to make it easier to track, I bundle them up and put all
the scattered patches into a single patchset.
Changes for v5:
-drop the check for delta != 0 in xfs_trans_dqresv().
Changes for v4:
-delete duplicated tp->t_dqinfo null check and allocation in one
patch.
-drop the first two patches that have been applied.
Changes for v3:
-add a separate patch to delete duplicated tp->t_dqinfo null check
and allocation.
Changes for v2:
-add the ASSERT for the arguments O_{u,g,p}dqpp.
-fix the strange indent.
-remove the XFS_TRANS_DQ_DIRTY flag.
-add more commit log description for delta judgement.
Kaixu Xia (3):
xfs: delete duplicated tp->t_dqinfo null check and allocation
xfs: check tp->t_dqinfo value instead of the XFS_TRANS_DQ_DIRTY flag
xfs: directly return if the delta equal to zero
fs/xfs/libxfs/xfs_shared.h | 1 -
fs/xfs/xfs_inode.c | 8 +------
fs/xfs/xfs_trans_dquot.c | 46 ++++++++++++--------------------------
3 files changed, 15 insertions(+), 40 deletions(-)
--
2.20.0
next reply other threads:[~2020-10-10 3:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 2:54 xiakaixu1987 [this message]
2020-10-10 2:54 ` [PATCH v5 1/3] xfs: delete duplicated tp->t_dqinfo null check and allocation xiakaixu1987
2020-10-15 8:22 ` Christoph Hellwig
2020-10-16 2:57 ` kaixuxia
2020-10-10 2:54 ` [PATCH v5 2/3] xfs: check tp->t_dqinfo value instead of the XFS_TRANS_DQ_DIRTY flag xiakaixu1987
2020-10-15 8:23 ` Christoph Hellwig
2020-10-10 2:54 ` [PATCH v5 3/3] xfs: directly return if the delta equal to zero xiakaixu1987
2020-10-15 8:25 ` Christoph Hellwig
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=1602298461-32576-1-git-send-email-kaixuxia@tencent.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;
as well as URLs for NNTP newsgroup(s).