From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/6] xfs: call xfs_qm_dqattach before performing reflink operations
Date: Tue, 23 Jan 2018 07:05:57 -0500 [thread overview]
Message-ID: <20180123120557.GC31825@bfoster.bfoster> (raw)
In-Reply-To: <151651284994.28390.7445163994259507169.stgit@magnolia>
On Sat, Jan 20, 2018 at 09:34:10PM -0800, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Ensure that we've attached all the necessary dquots before performing
> reflink operations so that quota accounting is accurate.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> fs/xfs/xfs_reflink.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
>
> diff --git a/fs/xfs/xfs_reflink.c b/fs/xfs/xfs_reflink.c
> index 5d1ff5a..947d0637 100644
> --- a/fs/xfs/xfs_reflink.c
> +++ b/fs/xfs/xfs_reflink.c
> @@ -54,6 +54,7 @@
> #include "xfs_rmap_btree.h"
> #include "xfs_sb.h"
> #include "xfs_ag_resv.h"
> +#include "xfs_qm.h"
>
> /*
> * Copy on Write of Shared Blocks
> @@ -282,6 +283,10 @@ xfs_reflink_reserve_cow(
> * tree.
> */
>
> + error = xfs_qm_dqattach_locked(ip, 0);
> + if (error)
> + return error;
> +
The same call exists further down in the function. Was the intent to
move it? I suspect we don't need it twice, at least.
> if (!xfs_iext_lookup_extent(ip, ifp, imap->br_startoff, &icur, &got))
> eof = true;
> if (!eof && got.br_startoff <= imap->br_startoff) {
> @@ -396,6 +401,10 @@ xfs_reflink_allocate_cow(
> ASSERT(xfs_is_reflink_inode(ip));
> ASSERT(xfs_isilocked(ip, XFS_ILOCK_EXCL | XFS_ILOCK_SHARED));
>
> + error = xfs_qm_dqattach_locked(ip, 0);
> + if (error)
> + return error;
> +
Similar pattern here, but for this one the assert above suggests we
could have the shared lock. xfs_qm_dqattach_locked() looks like it
expects the exclusive lock (and that's what it looks like the second
call deals with). Hm?
Brian
> /*
> * Even if the extent is not shared we might have a preallocation for
> * it in the COW fork. If so use it.
> @@ -1356,6 +1365,14 @@ xfs_reflink_remap_range(
> if (IS_DAX(inode_in) || IS_DAX(inode_out))
> goto out_unlock;
>
> + /* Attach dquots to both inodes */
> + ret = xfs_qm_dqattach(src, 0);
> + if (ret)
> + goto out_unlock;
> + ret = xfs_qm_dqattach(dest, 0);
> + if (ret)
> + goto out_unlock;
> +
> ret = vfs_clone_file_prep_inodes(inode_in, pos_in, inode_out, pos_out,
> &len, is_dedupe);
> if (ret <= 0)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-01-23 12:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 5:33 [PATCH 0/6] xfs: reflink fixes Darrick J. Wong
2018-01-21 5:33 ` [PATCH 1/6] xfs: reflink should break pnfs leases before sharing blocks Darrick J. Wong
2018-01-23 12:05 ` Brian Foster
2018-01-23 18:19 ` Darrick J. Wong
2018-01-21 5:34 ` [PATCH 2/6] xfs: only grab shared inode locks for source file during reflink Darrick J. Wong
2018-01-23 12:05 ` Brian Foster
2018-01-23 18:23 ` Darrick J. Wong
2018-01-21 5:34 ` [PATCH 3/6] xfs: call xfs_qm_dqattach before performing reflink operations Darrick J. Wong
2018-01-23 12:05 ` Brian Foster [this message]
2018-01-23 18:27 ` Darrick J. Wong
2018-01-21 5:34 ` [PATCH 4/6] xfs: CoW fork operations should only update quota reservations Darrick J. Wong
2018-01-21 5:34 ` [PATCH 5/6] xfs: track CoW blocks separately in the inode Darrick J. Wong
2018-01-21 5:34 ` [PATCH 6/6] xfs: fix up cowextsz allocation shortfalls Darrick J. Wong
2018-01-22 23:25 ` [PATCH 0/6] xfs: reflink fixes Darrick J. Wong
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=20180123120557.GC31825@bfoster.bfoster \
--to=bfoster@redhat.com \
--cc=darrick.wong@oracle.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