Merge ~ahasenack/ubuntu/+source/cyrus-sasl2:xenial-saslauthd-cpu-usage-997217 into ubuntu/+source/cyrus-sasl2:ubuntu/xenial-devel
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Andreas Hasenack | ||||
Approved revision: | fe2f4e2bff93cee0ccf49da2d1b27984cca64cde | ||||
Merge reported by: | Andreas Hasenack | ||||
Merged at revision: | fe2f4e2bff93cee0ccf49da2d1b27984cca64cde | ||||
Proposed branch: | ~ahasenack/ubuntu/+source/cyrus-sasl2:xenial-saslauthd-cpu-usage-997217 | ||||
Merge into: | ubuntu/+source/cyrus-sasl2:ubuntu/xenial-devel | ||||
Diff against target: | 0 lines | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Christian Ehrhardt (community) | Approve | ||
Canonical Server | Pending | ||
Review via email: mp+357779@code.launchpad.net |
Description of the change
Please use git for the review and ignore the launchpad diff, as it's incorrect.
Add an upstream patch to fix a condition where saslauthd could be stuck in a loop when the imap server went away.
This affected precise, which has a patch that introduced the loop, but with no exit clause (in that scenario when the imap server goes away).
Then trusty improved on that patch by adding a loop counter and exiting if that counter is hit, so trusty is not affected.
Eventually upstream adopted the original fix with no loop counter and reintroduced the bug. This was packaged for xenial, where the good trusty patch was dropped because it was deemed to be already applied in upstream.
Bionic onwards finally has the upstream version which added one last fix, and this is the fix I'm applying to the xenial package now.
Trusty still loops, but because of the loop counter, that is contained.
https:/
Testing instructions are in the bug.
Bileto ticket and PPA for testing: https:/
I wonder about the test errors, but it might be an evil rabbit hole as usual. autopkgtest. ubuntu. com/packages/ k/kldap/ xenial/ i386 autopkgtest. ubuntu. com/packages/ q/qca2/ xenial/ i386
They look good on xenial:
http://
http://
But are broken in https:/ /bileto. ubuntu. com/excuses/ 3498/xenial. html
But the tests hit things not directly touched by you I think.
One is on an ABI checker and one is actually a build error of the tests.
I'm afraid there is some extra work ahead on this :-/