Message ID | 20210823123516.969486-4-hch@lst.de (mailing list archive) |
---|---|
State | Superseded |
Headers | show |
Series | [1/9] fsdax: improve the FS_DAX Kconfig description and help text | expand |
On Mon, Aug 23, 2021 at 5:39 AM Christoph Hellwig <hch@lst.de> wrote: > > There is no point in trying to finding the dax device if the DAX flag is > not set on the queue as none of the users of the device mapper exported > block devices could make use of the DAX capability. Looks good, Reviewed-by: Dan Williams <dan.j.williams@intel.com>
diff --git a/drivers/md/dm.c b/drivers/md/dm.c index 2c5f9e585211..465714341300 100644 --- a/drivers/md/dm.c +++ b/drivers/md/dm.c @@ -650,7 +650,7 @@ static int open_table_device(struct table_device *td, dev_t dev, } td->dm_dev.bdev = bdev; - td->dm_dev.dax_dev = dax_get_by_host(bdev->bd_disk->disk_name); + td->dm_dev.dax_dev = fs_dax_get_by_bdev(bdev); return 0; }
There is no point in trying to finding the dax device if the DAX flag is not set on the queue as none of the users of the device mapper exported block devices could make use of the DAX capability. Signed-off-by: Christoph Hellwig <hch@lst.de> --- drivers/md/dm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)