Thanks for the reply. As regards 1535989, as I understand that fix is included in 0.4.9-3ubuntu7.14 and I am able to reproduce the issue in that build.
When it comes to reproducing the issue, currently I have something that cannot easily be replicated outside my test environment. Basically my environment has a number (specifically 4) of iSCSI targets serving the same drives available on the network. This test is a loop that randomly either does an iSCSI login to all the paths available for a drive that is available, or does an iSCSI logout to all paths on the device. In turn multipathd processes the path additions or removals triggering the issue. I think that the issue in commit cb0f7127ba90ab5e8e71fc534a0a16cdbe96a88f is triggered by multipathd processing a path addition to any iSCSI device. I don't think a SIGSEGV is reproducible from this issue alone, but the valgrind/memcheck report of free-after-use is. I think that the issue in commit 828d2fbaab304d1ec7db2f563a59eaf2c7a516ea would be triggered by mulitpathd processing any path removal from a multipath with multiple paths and is not about iSCSI in particular. In the iSCSI context the path removal is a consequence of an iSCSI logout rather than a physical reconfiguration. I think this is the issue causing the SIGSEGV in practice. Let me see if I can isolate a test script than can be used standalone and ideally be incorporated into any regression suite you have. It may take a couple of business days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628723 Title: Trusty: multipathd SIGSEGV on path addition or removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1628723/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
