diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2019-12-13 14:13:15 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2019-12-13 14:13:15 -0800 |
commit | 15da849c910da05622c75c5741dd6e176a8b6fe2 (patch) | |
tree | 62541d69d79a3327120b8e406709fd0749e7b069 /fs | |
parent | 22ff311af9c7d0eca4e9d276e95c4793a6ecf84f (diff) | |
parent | 7fc979f8204fb763e203d3e716c17d352eb96b35 (diff) | |
download | linux-stable-15da849c910da05622c75c5741dd6e176a8b6fe2.tar.gz linux-stable-15da849c910da05622c75c5741dd6e176a8b6fe2.tar.bz2 linux-stable-15da849c910da05622c75c5741dd6e176a8b6fe2.zip |
Merge tag 'for-5.5/dm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm
Pull device mapper fixes from Mike Snitzer:
- Fix DM multipath by restoring full path selector functionality for
bio-based configurations that don't haave a SCSI device handler.
- Fix dm-btree removal to ensure non-root btree nodes have at least
(max_entries / 3) entries. This resolves userspace thin_check
utility's report of "too few entries in btree_node".
- Fix both the DM thin-provisioning and dm-clone targets to properly
flush the data device prior to metadata commit. This resolves the
potential for inconsistency across a power loss event when the data
device has a volatile writeback cache.
- Small documentation fixes to dm-clone and dm-integrity.
* tag 'for-5.5/dm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm:
docs: dm-integrity: remove reference to ARC4
dm thin: Flush data device before committing metadata
dm thin metadata: Add support for a pre-commit callback
dm clone: Flush destination device before committing metadata
dm clone metadata: Use a two phase commit
dm clone metadata: Track exact changes per transaction
dm btree: increase rebalance threshold in __rebalance2()
dm: add dm-clone to the documentation index
dm mpath: remove harmful bio-based optimization
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions