#2445 Race condition while invalidating memory cache in client code
Closed: Fixed None Opened 5 years ago by lslebodn.

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

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

Fields changed

status: new => assigned

Fields changed

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

2 years ago

Login to comment on this ticket.