You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ticket was cloned from Red Hat Bugzilla: Bug 1586127
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
Ticket was cloned from Red Hat Bugzilla: Bug 1586127
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
There is a check in the memory cache code that checks if a record pointer points to the mmapped region . But since some time ago, we return not a pointer to the mmapped region itself, but a copy to avoid issues with invalidating an entry while the same entry is being returned.
In most cases, the check is correct, simply because of how memory is laid out on Linux, but in some cases the check was failing and causing a high load of SSSD.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/3776
Ticket was cloned from Red Hat Bugzilla: Bug 1586127
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
Ticket was cloned from Red Hat Bugzilla: Bug 1586127
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
There is a check in the memory cache code that checks if a record pointer points to the mmapped region . But since some time ago, we return not a pointer to the mmapped region itself, but a copy to avoid issues with invalidating an entry while the same entry is being returned.
In most cases, the check is correct, simply because of how memory is laid out on Linux, but in some cases the check was failing and causing a high load of SSSD.
Comments
Comment from jhrozek at 2018-07-20 12:03:33
Metadata Update from @jhrozek:
Comment from jhrozek at 2018-07-20 17:33:55
PR: #622
Comment from jhrozek at 2018-07-20 17:33:56
Metadata Update from @jhrozek:
Comment from jhrozek at 2018-07-30 22:18:16
Comment from jhrozek at 2018-08-02 12:53:13
Metadata Update from @jhrozek:
The text was updated successfully, but these errors were encountered: