dm snap: add fake origin_direct_access
authorToshi Kani <toshi.kani@hpe.com>
Tue, 28 Jun 2016 19:37:16 +0000 (13:37 -0600)
committerMike Snitzer <snitzer@redhat.com>
Thu, 21 Jul 2016 03:49:51 +0000 (23:49 -0400)
commitf6e629bd2379dceb547be93915314307871a7f6c
tree3a2ef8ed074e273c081eca2ca0adfd4bce6f561d
parentbeec25b4573bc310f5a12cf33207b20ecc30945c
dm snap: add fake origin_direct_access

dax-capable mapped-device is marked as DM_TYPE_DAX_BIO_BASED,
which supports both dax and bio-based operations.  dm-snap
needs to work with dax-capable device when bio-based operation
is used.

Add fake origin_direct_access() to origin device so that its
origin device is also marked as DM_TYPE_DAX_BIO_BASED for
dax-capable device.  This allows to extend target's DM table.
dm-snap works normally when bio-based operation is used.

dm-snap does not support dax operation, and mount with dax
option to a target device or snapshot device fails.

Signed-off-by: Toshi Kani <toshi.kani@hpe.com>
Cc: Mike Snitzer <snitzer@redhat.com>
Cc: Alasdair Kergon <agk@redhat.com>
Cc: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
drivers/md/dm-snap.c