Andreas Gruenbacher 856473cd5d iomap: Make sure iomap_end is called after iomap_begin ...

Make sure iomap_end is always called when iomap_begin succeeds.

Without this fix, iomap_end won't be called when a filesystem's
iomap_begin operation returns an invalid mapping, bypassing any
unlocking done in iomap_end.  With this fix, the unlocking will still
happen.

This bug was found by Bob Peterson during code review.  It's unlikely
that such iomap_begin bugs will survive to affect users, so backporting
this fix seems unnecessary.

Fixes: ae259a9c8593 ("fs: introduce iomap infrastructure")
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>

2020-07-06 10:49:27 -07:00

..

apply.c

iomap: Make sure iomap_end is called after iomap_begin

2020-07-06 10:49:27 -07:00

buffered-io.c

New code for 5.8:

2020-06-13 12:44:30 -07:00

direct-io.c

for-5.8-tag

2020-06-02 19:59:25 -07:00

fiemap.c

fs: handle FIEMAP_FLAG_SYNC in fiemap_prep

2020-06-03 23:16:55 -04:00

Makefile

iomap: lift common tracing code from xfs to iomap

2019-10-21 08:51:59 -07:00

seek.c

iomap: use a srcmap for a read-modify-write I/O

2019-10-21 08:51:59 -07:00

swapfile.c

iomap: use a srcmap for a read-modify-write I/O

2019-10-21 08:51:59 -07:00

trace.c

iomap: lift common tracing code from xfs to iomap

2019-10-21 08:51:59 -07:00

trace.h

iomap: convert from readpages to readahead

2020-06-02 10:59:07 -07:00