summaryrefslogtreecommitdiffstats
path: root/arch/x86/lib
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2020-09-20 15:01:57 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2020-09-20 15:01:57 -0700
commit4a123dbaf3a6efca717e3a5ac8176fd4897456b2 (patch)
tree3f935ae02d044652b14b7c39ab6e893fcd4e3028 /arch/x86/lib
parentbdcf11de8f776152c82d2197b255c2d04603f976 (diff)
parentd4c5da5049ac27c6ef8f6f98548c3a1ade352d25 (diff)
downloadlinux-4a123dbaf3a6efca717e3a5ac8176fd4897456b2.tar.bz2
Merge tag 'libnvdimm-fixes-5.9-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
Pull libnvdimm fixes from Dan Williams: "A handful of fixes to address a string of mistakes in the mechanism for device-mapper to determine if its component devices are dax capable. - Fix an original bug in device-mapper table reference counting when interrogating dax capability in the component device. This bug was hidden by the following bug. - Fix device-mapper to use the proper helper (dax_supported() instead of the leaf helper generic_fsdax_supported()) to determine dax operation of a stacked block device configuration. The original implementation is only valid for one level of dax-capable block device stacking. This bug was discovered while fixing the below regression. - Fix an infinite recursion regression introduced by broken attempts to quiet the generic_fsdax_supported() path and make it bail out before logging "dax capability not found" errors" * tag 'libnvdimm-fixes-5.9-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm: dax: Fix stack overflow when mounting fsdax pmem device dm: Call proper helper to determine dax support dm/dax: Fix table reference counts
Diffstat (limited to 'arch/x86/lib')
0 files changed, 0 insertions, 0 deletions