iomap: inline data should be an iomap type, not a flag

Inline data is fundamentally different from our normal mapped case in that
it doesn't even have a block address.  So instead of having a flag for it
it should be an entirely separate iomap range type.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>

1 files changed, 1 insertions, 1 deletions

diff --git a/include/linux/iomap.h b/include/linux/iomap.h
index 4bd87294219a..8f7095fc514e 100644
--- a/include/linux/iomap.h
+++ b/include/linux/iomap.h
@@ -18,6 +18,7 @@ struct vm_fault;
 #define IOMAP_DELALLOC  0x02    /* delayed allocation blocks */
 #define IOMAP_MAPPED    0x03    /* blocks allocated at @addr */
 #define IOMAP_UNWRITTEN 0x04    /* blocks allocated at @addr in unwritten state */
+#define IOMAP_INLINE    0x05    /* data inline in the inode */
 
 /*
  * Flags for all iomap mappings:
@@ -34,7 +35,6 @@ struct vm_fault;
  */
 #define IOMAP_F_MERGED          0x10    /* contains multiple blocks/extents */
 #define IOMAP_F_SHARED          0x20    /* block shared with another file */
-#define IOMAP_F_DATA_INLINE     0x40    /* data inline in the inode */
 
 /*
  * Magic value for addr: