From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Jan Kara <jack@suse.cz>,
linux-nvdimm@lists.01.org, Dave Chinner <david@fromorbit.com>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
Jeff Moyer <jmoyer@redhat.com>,
luto@kernel.org, linux-fsdevel@vger.kernel.org,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2 5/5] xfs: toggle XFS_DIFLAG2_IOMAP_IMMUTABLE in response to fallocate
Date: Fri, 4 Aug 2017 13:14:12 -0700 [thread overview]
Message-ID: <20170804201412.GE24087@magnolia> (raw)
In-Reply-To: <150181371519.32119.2762945986660101008.stgit@dwillia2-desk3.amr.corp.intel.com>
On Thu, Aug 03, 2017 at 07:28:35PM -0700, Dan Williams wrote:
> After validating the state of the file as not having holes, shared
> extents, or active mappings try to commit the
> XFS_DIFLAG2_IOMAP_IMMUTABLE flag to the on-disk inode metadata. If that
> succeeds then allow the S_IOMAP_IMMUTABLE to be set on the vfs inode.
>
> Cc: Jan Kara <jack@suse.cz>
> Cc: Jeff Moyer <jmoyer@redhat.com>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
> Suggested-by: Dave Chinner <david@fromorbit.com>
> Suggested-by: "Darrick J. Wong" <darrick.wong@oracle.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
> fs/xfs/xfs_bmap_util.c | 32 ++++++++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
> diff --git a/fs/xfs/xfs_bmap_util.c b/fs/xfs/xfs_bmap_util.c
> index 70ac2d33ab27..8464c25a2403 100644
> --- a/fs/xfs/xfs_bmap_util.c
> +++ b/fs/xfs/xfs_bmap_util.c
> @@ -1436,9 +1436,11 @@ xfs_seal_file_space(
> xfs_off_t offset,
> xfs_off_t len)
> {
> + struct xfs_mount *mp = ip->i_mount;
> struct inode *inode = VFS_I(ip);
> struct address_space *mapping = inode->i_mapping;
> int error;
> + struct xfs_trans *tp;
>
> ASSERT(xfs_isilocked(ip, XFS_MMAPLOCK_EXCL));
>
> @@ -1454,6 +1456,10 @@ xfs_seal_file_space(
> if (error)
> return error;
>
> + error = xfs_trans_alloc(mp, &M_RES(mp)->tr_ichange, 0, 0, 0, &tp);
> + if (error)
> + return error;
> +
> xfs_ilock(ip, XFS_ILOCK_EXCL);
> /*
> * Either the size changed after we performed allocation /
> @@ -1486,10 +1492,20 @@ xfs_seal_file_space(
> if (error < 0)
> goto out_unlock;
>
> + xfs_trans_ijoin(tp, ip, 0);
FWIW if you change that third parameter to XFS_ILOCK_EXCL then
xfs_trans_commit will do the xfs_iunlock(ip, XFS_ILOCK_EXCL) for you if
the commit succeeds...
> + ip->i_d.di_flags2 |= XFS_DIFLAG2_IOMAP_IMMUTABLE;
> + xfs_trans_log_inode(tp, ip, XFS_ILOG_CORE);
> + error = xfs_trans_commit(tp);
> + tp = NULL; /* nothing to cancel */
> + if (error)
> + goto out_unlock;
> +
> inode->i_flags |= S_IOMAP_IMMUTABLE;
...and then you can just return out here.
--D
> out_unlock:
> xfs_iunlock(ip, XFS_ILOCK_EXCL);
> + if (tp)
> + xfs_trans_cancel(tp);
>
> return error;
> }
> @@ -1500,15 +1516,21 @@ xfs_unseal_file_space(
> xfs_off_t offset,
> xfs_off_t len)
> {
> + struct xfs_mount *mp = ip->i_mount;
> struct inode *inode = VFS_I(ip);
> struct address_space *mapping = inode->i_mapping;
> int error;
> + struct xfs_trans *tp;
>
> ASSERT(xfs_isilocked(ip, XFS_MMAPLOCK_EXCL));
>
> if (offset)
> return -EINVAL;
>
> + error = xfs_trans_alloc(mp, &M_RES(mp)->tr_ichange, 0, 0, 0, &tp);
> + if (error)
> + return error;
> +
> xfs_ilock(ip, XFS_ILOCK_EXCL);
> /*
> * It does not make sense to unseal less than the full range of
> @@ -1527,11 +1549,21 @@ xfs_unseal_file_space(
> if (mapping_mapped(mapping))
> goto out_unlock;
>
> + xfs_trans_ijoin(tp, ip, 0);
> + ip->i_d.di_flags2 &= ~XFS_DIFLAG2_IOMAP_IMMUTABLE;
> + xfs_trans_log_inode(tp, ip, XFS_ILOG_CORE);
> + error = xfs_trans_commit(tp);
> + tp = NULL; /* nothing to cancel */
> + if (error)
> + goto out_unlock;
> +
> inode->i_flags &= ~S_IOMAP_IMMUTABLE;
> error = 0;
>
> out_unlock:
> xfs_iunlock(ip, XFS_ILOCK_EXCL);
> + if (tp)
> + xfs_trans_cancel(tp);
>
> return error;
> }
>
> --
> 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:[~2017-08-04 20:14 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 2:28 [PATCH v2 0/5] fs, xfs: block map immutable files for dax, dma-to-storage, and swap Dan Williams
2017-08-04 2:28 ` [PATCH v2 1/5] fs, xfs: introduce S_IOMAP_IMMUTABLE Dan Williams
2017-08-04 20:00 ` Darrick J. Wong
2017-08-04 20:31 ` Dan Williams
2017-08-05 9:47 ` Christoph Hellwig
2017-08-07 0:25 ` Dave Chinner
2017-08-11 10:34 ` Christoph Hellwig
2017-08-04 2:28 ` [PATCH v2 2/5] fs, xfs: introduce FALLOC_FL_SEAL_BLOCK_MAP Dan Williams
2017-08-04 19:46 ` Darrick J. Wong
2017-08-04 19:52 ` Dan Williams
2017-08-04 23:31 ` Dave Chinner
2017-08-04 23:43 ` Dan Williams
2017-08-05 0:04 ` Dave Chinner
2017-08-04 2:28 ` [PATCH v2 3/5] fs, xfs: introduce FALLOC_FL_UNSEAL_BLOCK_MAP Dan Williams
2017-08-04 20:04 ` Darrick J. Wong
2017-08-04 20:36 ` Dan Williams
2017-08-04 2:28 ` [PATCH v2 4/5] xfs: introduce XFS_DIFLAG2_IOMAP_IMMUTABLE Dan Williams
2017-08-04 20:33 ` Darrick J. Wong
2017-08-04 20:45 ` Dan Williams
2017-08-04 23:46 ` Dave Chinner
2017-08-04 23:57 ` Darrick J. Wong
2017-08-04 2:28 ` [PATCH v2 5/5] xfs: toggle XFS_DIFLAG2_IOMAP_IMMUTABLE in response to fallocate Dan Williams
2017-08-04 20:14 ` Darrick J. Wong [this message]
2017-08-04 20:47 ` Dan Williams
2017-08-04 20:53 ` Darrick J. Wong
2017-08-04 20:55 ` Dan Williams
2017-08-04 2:38 ` [PATCH v2 0/5] fs, xfs: block map immutable files for dax, dma-to-storage, and swap Dan Williams
2017-08-05 9:50 ` Christoph Hellwig
2017-08-06 18:51 ` Dan Williams
2017-08-11 10:44 ` Christoph Hellwig
2017-08-11 22:26 ` Dan Williams
2017-08-12 3:57 ` Andy Lutomirski
2017-08-12 4:44 ` Dan Williams
2017-08-12 7:34 ` Christoph Hellwig
2017-08-12 7:33 ` Christoph Hellwig
2017-08-12 19:19 ` Dan Williams
2017-08-13 9:24 ` Christoph Hellwig
2017-08-13 20:31 ` Dan Williams
2017-08-14 12:40 ` Jan Kara
2017-08-14 16:14 ` Dan Williams
2017-08-15 8:37 ` Jan Kara
2017-08-15 23:50 ` Dan Williams
2017-08-16 13:57 ` Jan Kara
2017-08-21 9:16 ` Peter Zijlstra
2017-08-14 21:46 ` Darrick J. Wong
2017-08-13 23:46 ` Dave Chinner
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=20170804201412.GE24087@magnolia \
--to=darrick.wong@oracle.com \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jmoyer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-xfs@vger.kernel.org \
--cc=luto@kernel.org \
--cc=ross.zwisler@linux.intel.com \
/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).