[Ubuntu-ha] [Bug 1877280] Re: attrd can segfault on exit
Hello Dan, or anyone else affected, Accepted pacemaker into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pacemaker/1.1.14-2ubuntu1.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: pacemaker (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1877280 Title: attrd can segfault on exit Status in pacemaker package in Ubuntu: Fix Released Status in pacemaker source package in Xenial: Fix Committed Bug description: [impact] pacemaker's attrd may segfault on exit. [test case] this is a follow on to bug 1871166, the patches added there prevented one segfault but this one emerged. As with that bug, I can't reproduce this myself, but the original reporter is able to reproduce intermittently. [regression potential] any regression would likely impact the exit path of attrd, possibly causing a segfault or other incorrect exit. [scope] this is needed only for Xenial. this is fixed upstream by commit 3c62fb1d0d which is included in Bionic and later. [other info] this is a follow on to bug 1871166. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1877280/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1871166] Update Released
The verification of the Stable Release Update for pacemaker has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1871166 Title: lrmd crashes Status in pacemaker package in Ubuntu: Fix Released Status in pacemaker source package in Xenial: Fix Released Bug description: [impact] lrmd crashes and dumps core. [test case] I can not reproduce, but it is reproducable in the specific setup of the person reporting the bug to me. [regression potential] this patches the cancel/cleanup part of the code, so regressions would likely involve possible memory leaks (instead of use-after-free segfaults), failure to correctly cancel or cleanup operations, or other failure during cancel action. [scope] this is fixed by commits: 933d46ef20591757301784773a37e06b78906584 94a4c58f675d163085a055f59fd6c3a2c9f57c43 dc36d4375c049024a6f9e4d2277a3e6444fad05b deabcc5a6aa93dadf0b20364715b559a5b9848ac b85037b75255061a41d0ec3fd9b64f271351b43e which are all included starting with version 1.1.17, and Bionic includes version 1.1.18, so this is fixed already in Bionic and later. This is needed only for Xenial. [other info] As mentioned in the test case section, I do not have a setup where I'm able to reproduce this, but I can ask the initial reporter to test and verify the fix, and they have verified a test build fixed the problem for them. Also, the upstream commits removed two symbols, which I elided from the backported patches; those symbols are still available and, while it is unlikely there were any users of those symbols outside pacemaker itself, this change should not break any possible external users. See patch 0002 header in the upload for more detail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1871166/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1871166] Re: lrmd crashes
This bug was fixed in the package pacemaker - 1.1.14-2ubuntu1.7 --- pacemaker (1.1.14-2ubuntu1.7) xenial; urgency=medium [ Victor Tapia ] * d/p/lp1871166/0001-Fix-libservices-prevent-use-after-free-when-freeing-.patch, d/p/lp1871166/0002-Fix-libservices-ensure-completed-ops-aren-t-on-block.patch, d/p/lp1871166/0003-Refactor-libservices-handle-in-flight-case-first-whe.patch, d/p/lp1871166/0004-Fix-libservices-properly-cancel-in-flight-systemd-up.patch, d/p/lp1871166/0005-Fix-libservices-properly-detect-in-flight-systemd-up.patch: - prevent use-after-free segfault (LP: #1871166) -- Dan Streetman Mon, 06 Apr 2020 13:37:40 -0400 ** Changed in: pacemaker (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1871166 Title: lrmd crashes Status in pacemaker package in Ubuntu: Fix Released Status in pacemaker source package in Xenial: Fix Released Bug description: [impact] lrmd crashes and dumps core. [test case] I can not reproduce, but it is reproducable in the specific setup of the person reporting the bug to me. [regression potential] this patches the cancel/cleanup part of the code, so regressions would likely involve possible memory leaks (instead of use-after-free segfaults), failure to correctly cancel or cleanup operations, or other failure during cancel action. [scope] this is fixed by commits: 933d46ef20591757301784773a37e06b78906584 94a4c58f675d163085a055f59fd6c3a2c9f57c43 dc36d4375c049024a6f9e4d2277a3e6444fad05b deabcc5a6aa93dadf0b20364715b559a5b9848ac b85037b75255061a41d0ec3fd9b64f271351b43e which are all included starting with version 1.1.17, and Bionic includes version 1.1.18, so this is fixed already in Bionic and later. This is needed only for Xenial. [other info] As mentioned in the test case section, I do not have a setup where I'm able to reproduce this, but I can ask the initial reporter to test and verify the fix, and they have verified a test build fixed the problem for them. Also, the upstream commits removed two symbols, which I elided from the backported patches; those symbols are still available and, while it is unlikely there were any users of those symbols outside pacemaker itself, this change should not break any possible external users. See patch 0002 header in the upload for more detail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1871166/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
