Learn more about these different git repos.
Other Git URLs
If caches is invalidated with command sss_cache -U (-G or -E) then client code will need to reinitialize fast memory cache. Thread safe initialisation was fixed in ticket #2380. The 1st thread find out then memory cache should be reinitialized; therefore it fast memory cached is unmapped and context destroyed. In the same time, 2nd thread tried to check header of memory cache whether it was initialized and valid. As a result of previously unmapped memory 2nd thread access memory out of bound. (SEGFAULT)
Fields changed
mark: => 0 milestone: NEEDS_TRIAGE => SSSD 1.12.2 owner: somebody => lslebodn
We need to do a release as requested by downstream. Moving tickets that are not fixed already or very close to acking to 1.12.3
milestone: SSSD 1.12.2 => SSSD 1.12.3
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1123291 (Red Hat Enterprise Linux 6)
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1123291 1123291]
This upstream ticket was requesting by a downstream. Bumping the priority to make sure the ticket is closed as soon as possible.
priority: major => critical
status: new => assigned
patch: 0 => 1
resolution: => fixed status: assigned => closed
Metadata Update from @lslebodn: - Issue assigned to lslebodn - Issue set to the milestone: SSSD 1.12.3
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/3487
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.