lrmd crashes

This looks good, though this is quite a lot of code changes (and refactoring) for a bug without a clear reproduction scenario. Would it be possible to, along with the verification to be done by the reporting person, perform some sanity runs to make sure the cancel/cleanup parts of the code did not regress? Thanks!

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.7 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.

Status update - still waiting on original reporter to perform testing with -proposed package.

The original reporter has performed testing and verified that the original crash no longer happens with the package in proposed, so I am marking this as verified.

Please note that a *new* crash has been reported, and is being worked in bug 1877280. It is *not* a regression caused by the patches from this bug; the fixes in this bug simply allowed the code to proceed further and, in some cases, crash at a later point, which is fixed by patches included in the new bug.

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 <email address hidden> Mon, 06 Apr 2020 13:37:40 -0400

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.