We've run into various problems due to the fact that the reflink remap code reuses the xfs_bmapi_write codepath for setting up the extent list entries and abuses the firstblock field for that purpose. This series fixes this by creating an entirely separate xfs_bmapi_remap path that is much simpler than xfs_bmapi_write and does not need to overload the firstblock field. Changes since V2: - add a missing call to xfs_iread_extents Changes since V1: - warn when encountering invalid forks in bmap item recovery - tidy up the xfs_bmap_add_extent_hole_real declaration - trivial indentation change in xfs_bmapi_remap -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
