As requested [1], break out the block specific updates from the dax-gup series [2], to merge via the block tree.
1/ Enable dax mappings for raw block devices. This addresses the review comments (from Ross and Honza) from the RFC [3]. 2/ Introduce dax_map_atomic() to fix races between device teardown and new mapping requests. This depends on commit 2a9067a91825 "block: generic request_queue reference counting" in for-4.4/integrity branch of the block tree. 3/ Cleanup clear_pmem() and its usage in dax. This depends on commit 0f90cc6609c7 "mm, dax: fix DAX deadlocks" that was merged into v4.3-rc6. These pass the nvdimm unit tests and have passed a 0day-kbuild-robot run. [1]: https://lists.01.org/pipermail/linux-nvdimm/2015-October/002531.html [2]: https://lists.01.org/pipermail/linux-nvdimm/2015-October/002387.html [3]: https://lists.01.org/pipermail/linux-nvdimm/2015-October/002512.html --- Dan Williams (5): pmem, dax: clean up clear_pmem() dax: increase granularity of dax_clear_blocks() operations block, dax: fix lifetime of in-kernel dax mappings with dax_map_atomic() block: introduce file_bd_inode() block: enable dax for raw block devices arch/x86/include/asm/pmem.h | 7 -- block/blk.h | 2 fs/block_dev.c | 73 ++++++++++++++-- fs/dax.c | 196 +++++++++++++++++++++++++++---------------- include/linux/blkdev.h | 2 5 files changed, 191 insertions(+), 89 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
