Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-dm
tags/dm-3.11-changes
to get the following device-mapper changes for 3.11.
Thanks,
Alasdair
----------------------------------------------------------------
Add a device-mapper target called dm-switch to provide a multipath
framework for storage arrays that dynamically reconfigure their
preferred paths for different device regions.
Fix a bug in the verity target that prevented its use with some
specific sizes of devices.
Improve some locking mechanisms in the device-mapper core and bufio.
Add Mike Snitzer as a device-mapper maintainer.
A few more clean-ups and fixes.
----------------------------------------------------------------
Alasdair G Kergon (2):
dm flakey: correct ctr alloc failure mesg
dm: update maintainers
Hannes Reinecke (1):
dm mpath: fix ioctl deadlock when no paths
Jim Ramsay (1):
dm: add switch target
Mikulas Patocka (9):
dm ioctl: set noio flag to avoid __vmalloc deadlock
dm verity: fix inability to use a few specific devices sizes
dm: use __GFP_HIGHMEM in __vmalloc
dm verity: remove pointless comparison
dm verity: use __ffs and __fls
dm cache: fix arm link errors with inline
dm bufio: submit writes outside lock
dm: optimize use SRCU and RCU
dm: optimize reorder structure
Documentation/device-mapper/switch.txt | 126 ++++++++
MAINTAINERS | 2 +
drivers/md/Kconfig | 14 +
drivers/md/Makefile | 1 +
drivers/md/dm-bufio.c | 75 ++++-
drivers/md/dm-cache-target.c | 4 +
drivers/md/dm-flakey.c | 2 +-
drivers/md/dm-ioctl.c | 127 +++++---
drivers/md/dm-mpath.c | 8 +-
drivers/md/dm-switch.c | 538 ++++++++++++++++++++++++++++++++
drivers/md/dm-table.c | 35 ---
drivers/md/dm-verity.c | 17 +-
drivers/md/dm.c | 177 ++++++-----
include/linux/device-mapper.h | 6 +-
include/uapi/linux/dm-ioctl.h | 4 +-
15 files changed, 951 insertions(+), 185 deletions(-)
create mode 100644 Documentation/device-mapper/switch.txt
create mode 100644 drivers/md/dm-switch.c
--
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/
