[Bug 789229] Re: using a blacklist and a blacklist_exception section results in multipathd filtering out paths it shouldn't

[Craig Magina]

** Changed in: multipath-tools (Ubuntu Natty)
       Status: Confirmed => In Progress

** Changed in: multipath-tools (Ubuntu Natty)
     Assignee: (unassigned) => Craig Magina (craig.magina)

** Patch added: "natty based debdiff of the fix"
   https://bugs.launchpad.net/ubuntu/maverick/+source/multipath-tools/+bug/789229/+attachment/2300791/+files/natty.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/789229

Title:
  using a blacklist and a blacklist_exception section results in
  multipathd filtering out paths it shouldn't

Status in “multipath-tools” package in Ubuntu:
  Fix Released
Status in “multipath-tools” source package in Lucid:
  In Progress
Status in “multipath-tools” source package in Maverick:
  In Progress
Status in “multipath-tools” source package in Natty:
  In Progress

Bug description:
  Binary package hint: multipath-tools

  The issue is due to a bug in some if/then logic in
  blacklist.c:_filter_path resulting in the routine returning a value
  other then 0 for anything found on the exceptions list.

  SRU Justification:
  1. Impact: a config which (correctly) finds an entry both in blacklist and blacklist exceptions will not honor the exception
  2. How bug was addressed: an upstream fix was pulled in.  The root cause was that return values from functions checking existence in blacklists were being misinterpreted.
  3. Minimal patch: see debdiff in comment #6.
  4. TEST CASE: Create a multipath config with /dev/sda in both blacklist and blacklist exception.  /dev/sda won't be used.
  5. Regression potential: this commit has been upstream since 2007, so should cause no regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/789229/+subscriptions