On Fri, Jan 08, 2021 at 10:55:00AM +0100, Christoph Hellwig wrote:

It happens on a dax_device.  We should not interwind dax and block_device
even more after a lot of good work has happened to detangle them.

I agree that the dax device should not be implied from the block device,
but what happens if regular block device drivers grow the ability to
(say) perform a background integrity scan and want to ->corrupted_range?

--D