SSSD / sssd

#2743 memory cache can work intermittently
Closed: Fixed Opened by lslebodn.

Closed: Fixed
Reopen Issue

There is an integrity check of records in memory cache.
It was introduced as part of workarounds (8a5931bcc8e9034e4beb92fc9addf3f7fcf83fd6) for crashes caused by corrupted memory cache. The corrupted memory cache was fixed in ticket #2049
but workaround with integrity check is still available.

The problem with integrity check is that it try to compare pointer from
memory cache with duplicate of record from memory cache. Sometime it can pass
and other times it needn't pass. It depends on memory allocator.

The result of wrong integrity check is that record is not considered to be valid and we fall back to responder. Result of this is regression from performace point of view.

  • master: ba847347cade817ee927397d82c952b51b0dcb2b

resolution: => fixed
status: new => closed

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13.1

Fields changed

rhbz: => 0

Metadata Update from @lslebodn:
- Issue set to the milestone: SSSD 1.13.1

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/3784

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.
Metadata
None
None
None
None
Normal
0
0
defect
SSSD
1.11.0
0
0
0
0
0
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.