From: Darrick J. Wong <darrick.wong@oracle.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 11/34] iomap: move IOMAP_F_BOUNDARY to gfs2
Date: Tue, 29 May 2018 22:50:33 -0700 [thread overview]
Message-ID: <20180530055033.GZ30110@magnolia> (raw)
In-Reply-To: <20180523144357.18985-12-hch@lst.de>
On Wed, May 23, 2018 at 04:43:34PM +0200, Christoph Hellwig wrote:
> Just define a range of fs specific flags and use that in gfs2 instead of
> exposing this internal flag flobally.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Looks ok to me, but better if the gfs2 folks [cc'd now] ack this...
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> ---
> fs/gfs2/bmap.c | 8 +++++---
> include/linux/iomap.h | 9 +++++++--
> 2 files changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/fs/gfs2/bmap.c b/fs/gfs2/bmap.c
> index cbeedd3cfb36..8efa6297e19c 100644
> --- a/fs/gfs2/bmap.c
> +++ b/fs/gfs2/bmap.c
> @@ -683,6 +683,8 @@ static void gfs2_stuffed_iomap(struct inode *inode, struct iomap *iomap)
> iomap->type = IOMAP_INLINE;
> }
>
> +#define IOMAP_F_GFS2_BOUNDARY IOMAP_F_PRIVATE
> +
> /**
> * gfs2_iomap_begin - Map blocks from an inode to disk blocks
> * @inode: The inode
> @@ -774,7 +776,7 @@ int gfs2_iomap_begin(struct inode *inode, loff_t pos, loff_t length,
> bh = mp.mp_bh[ip->i_height - 1];
> len = gfs2_extent_length(bh->b_data, bh->b_size, ptr, lend - lblock, &eob);
> if (eob)
> - iomap->flags |= IOMAP_F_BOUNDARY;
> + iomap->flags |= IOMAP_F_GFS2_BOUNDARY;
> iomap->length = (u64)len << inode->i_blkbits;
>
> out_release:
> @@ -846,12 +848,12 @@ int gfs2_block_map(struct inode *inode, sector_t lblock,
>
> if (iomap.length > bh_map->b_size) {
> iomap.length = bh_map->b_size;
> - iomap.flags &= ~IOMAP_F_BOUNDARY;
> + iomap.flags &= ~IOMAP_F_GFS2_BOUNDARY;
> }
> if (iomap.addr != IOMAP_NULL_ADDR)
> map_bh(bh_map, inode->i_sb, iomap.addr >> inode->i_blkbits);
> bh_map->b_size = iomap.length;
> - if (iomap.flags & IOMAP_F_BOUNDARY)
> + if (iomap.flags & IOMAP_F_GFS2_BOUNDARY)
> set_buffer_boundary(bh_map);
> if (iomap.flags & IOMAP_F_NEW)
> set_buffer_new(bh_map);
> diff --git a/include/linux/iomap.h b/include/linux/iomap.h
> index 13d19b4c29a9..819e0cd2a950 100644
> --- a/include/linux/iomap.h
> +++ b/include/linux/iomap.h
> @@ -27,8 +27,7 @@ struct vm_fault;
> * written data and requires fdatasync to commit them to persistent storage.
> */
> #define IOMAP_F_NEW 0x01 /* blocks have been newly allocated */
> -#define IOMAP_F_BOUNDARY 0x02 /* mapping ends at metadata boundary */
> -#define IOMAP_F_DIRTY 0x04 /* uncommitted metadata */
> +#define IOMAP_F_DIRTY 0x02 /* uncommitted metadata */
>
> /*
> * Flags that only need to be reported for IOMAP_REPORT requests:
> @@ -36,6 +35,12 @@ struct vm_fault;
> #define IOMAP_F_MERGED 0x10 /* contains multiple blocks/extents */
> #define IOMAP_F_SHARED 0x20 /* block shared with another file */
>
> +/*
> + * Flags from 0x1000 up are for file system specific usage:
> + */
> +#define IOMAP_F_PRIVATE 0x1000
> +
> +
> /*
> * Magic value for addr:
> */
> --
> 2.17.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-05-30 5:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180523144357.18985-1-hch@lst.de>
[not found] ` <20180523144357.18985-10-hch@lst.de>
2018-05-30 5:49 ` [Cluster-devel] [PATCH 09/34] iomap: inline data should be an iomap type, not a flag Darrick J. Wong
[not found] ` <20180523144357.18985-12-hch@lst.de>
2018-05-30 5:50 ` Darrick J. Wong [this message]
2018-05-30 9:30 ` [Cluster-devel] [PATCH 11/34] iomap: move IOMAP_F_BOUNDARY to gfs2 Steven Whitehouse
2018-05-30 9:59 ` Christoph Hellwig
2018-05-30 10:02 ` Steven Whitehouse
2018-05-30 10:10 ` Christoph Hellwig
2018-05-30 10:12 ` Steven Whitehouse
2018-05-30 11:03 ` Andreas Gruenbacher
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=20180530055033.GZ30110@magnolia \
--to=darrick.wong@oracle.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).