Hi Richard, the series looks fine to me, but it fails to address the root cause: that we have an inherently dangerous default for ->migratepage that assumes that file systems are implemented a certain way. I think the series should also grow a third patch to remove the default and just wire it up for the known good file systems, although we'd need some input on what known good is. Any idea what filesystems do get regular testing with code that's using CMA? A good approximation might be those that use the bufer_head based aops from fs/buffer.c -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
