On Mon, Oct 31, 2016 at 10:14:28AM -0400, Brian Foster wrote: > We've had reports of generic/095 causing XFS to BUG() in > __xfs_get_blocks() due to the existence of delalloc blocks on a direct > I/O read. generic/095 issues a mix of various types of I/O, including > direct and memory mapped I/O to a single file. Can you explain the scenario in which case this happens in a little more detail? The patch looks fine to me, but I'd really like to understand how this happens. -- 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
