summaryrefslogtreecommitdiff
path: root/lib/Kconfig.kmemcheck
diff options
context:
space:
mode:
authorMike Snitzer <snitzer@redhat.com>2011-03-24 13:54:33 +0000
committerAlasdair G Kergon <agk@redhat.com>2011-03-24 13:54:33 +0000
commita490a07a67b7a37f588021410e06b721a752fc34 (patch)
treece48096d6991f7e16bf100dd91cae9c10e37bf59 /lib/Kconfig.kmemcheck
parent19040c0bc8efcb767221d8ef7bb9c32ff0586179 (diff)
dm mpath: allow table load with no priority groups
This patch adjusts the multipath target to allow a table with both 0 priority groups and 0 for the initial priority group number. If any mpath device is held open when all paths in the last priority group have failed, userspace multipathd will attempt to reload the associated DM table to reflect the fact that the device no longer has any priority groups. But the reload attempt always failed because the multipath target did not allow 0 priority groups. All multipath target messages related to priority group (enable_group, disable_group, switch_group) will handle a priority group of 0 (will cause error). When reloading a multipath table with 0 priority groups, userspace multipathd must be updated to specify an initial priority group number of 0 (rather than 1). Signed-off-by: Mike Snitzer <snitzer@redhat.com> Cc: Babu Moger <babu.moger@lsi.com> Acked-by: Hannes Reinecke <hare@suse.de> Signed-off-by: Alasdair G Kergon <agk@redhat.com>
Diffstat (limited to 'lib/Kconfig.kmemcheck')
0 files changed, 0 insertions, 0 deletions