Re: [PATCH 1/9] iomap: add IOMAP_REPORT

[Christoph Hellwig <hch@lst.de>]

On Mon, Oct 10, 2016 at 06:45:46PM -0700, Darrick J. Wong wrote:
> On Mon, Oct 10, 2016 at 03:37:57PM +0200, Christoph Hellwig wrote:
> > 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 <hch@lst.de>
> > ---
> >  fs/iomap.c            |  2 +-
> >  include/linux/iomap.h | 17 +++++++++++------
> >  2 files changed, 12 insertions(+), 7 deletions(-)
> > 
> > diff --git a/fs/iomap.c b/fs/iomap.c
> > index 013d1d3..a922040 100644
> > --- a/fs/iomap.c
> > +++ b/fs/iomap.c
> > @@ -561,7 +561,7 @@ int iomap_fiemap(struct inode *inode, struct fiemap_extent_info *fi,
> >  	}
> >  
> >  	while (len > 0) {
> > -		ret = iomap_apply(inode, start, len, 0, ops, &ctx,
> > +		ret = iomap_apply(inode, start, len, IOMAP_REPORT, ops, &ctx,
> 
> Hmm.  /me notices that generic/352, generic/353, and generic/372 fail after
> this patchset is applied.  Will have a look at this tomorrow, unless this rings
> a bell?

I don't see any of those failures.