linux-toradex.git/include/linux/iomap.h, branch v4.9.16

iomap: add IOMAP_REPORT

2016-10-20T04:51:28+00:00

This allows the file system to tell a FIEMAP from a read operation, and thus
avoids the need to report flags that aren't actually used in the read path.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Darrick J. Wong 
Reviewed-by: Brian Foster 
Signed-off-by: Dave Chinner

Merge branch 'iomap-4.9-dax' into for-next

2016-10-02T22:53:59+00:00

iomap: add IOMAP_F_NEW flag

2016-09-19T01:24:37+00:00

Signed-off-by: Christoph Hellwig 
Reviewed-by: Ross Zwisler 
Signed-off-by: Dave Chinner

iomap: add a flag to report shared extents

2016-09-19T00:13:02+00:00

Signed-off-by: Darrick J. Wong 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Dave Chinner

fs: add iomap_file_dirty

2016-09-19T00:12:45+00:00

Originally-From: Christoph Hellwig 

This function uses the iomap infrastructure to re-write all pages
in a given range.  This is useful for doing a copy-up of COW ranges,
and might be useful for scrubbing in the future.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Dave Chinner 
Signed-off-by: Dave Chinner

iomap: don't set FIEMAP_EXTENT_MERGED for extent based filesystems

2016-08-29T01:33:58+00:00

Filesystems like XFS that use extents should not set the
FIEMAP_EXTENT_MERGED flag in the fiemap extent structures.  To allow
for both behaviors for the upcoming gfs2 usage split the iomap
type field into type and flags, and only set FIEMAP_EXTENT_MERGED if
the IOMAP_F_MERGED flag is set.  The flags field will also come in
handy for future features such as shared extents on reflink-enabled
file systems.

Reported-by: Andreas Gruenbacher 
Signed-off-by: Christoph Hellwig 
Acked-by: Darrick J. Wong 
Signed-off-by: Dave Chinner

fs: iomap based fiemap implementation

2016-06-20T23:38:45+00:00

Add a simple fiemap implementation based on iomap_ops, partially based
on a previous implementation from Bob Peterson .

Signed-off-by: Christoph Hellwig 
Reviewed-by: Dave Chinner 
Signed-off-by: Dave Chinner

fs: introduce iomap infrastructure

2016-06-20T23:23:11+00:00

Add infrastructure for multipage buffered writes.  This is implemented
using an main iterator that applies an actor function to a range that
can be written.

This infrastucture is used to implement a buffered write helper, one
to zero file ranges and one to implement the ->page_mkwrite VM
operations.  All of them borrow a fair amount of code from fs/buffers.
for now by using an internal version of __block_write_begin that
gets passed an iomap and builds the corresponding buffer head.

The file system is gets a set of paired ->iomap_begin and ->iomap_end
calls which allow it to map/reserve a range and get a notification
once the write code is finished with it.

Based on earlier code from Dave Chinner.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Bob Peterson 
Signed-off-by: Dave Chinner

fs: move struct iomap from exportfs.h to a separate header

2016-06-20T23:22:39+00:00

Signed-off-by: Christoph Hellwig 
Reviewed-by: Bob Peterson 
Signed-off-by: Dave Chinner