Description of problem:
The requests that the responders send to the Data Providers are allocated on
the global context to ensure that even if the client disconnects, there is
someone to read the reply. However, we forgot to free the structure that
represents the request, which meant that the sssd_nss process grew over time.
Version-Release number of selected component (if applicable):
1.9.2-4
How reproducible:
quite hard
Steps to Reproduce:
1. set a very low cache timeout
2. run account requests in parallel
3. observe the sssd_nss process growing
Actual results:
sssd_nss process is growing
Expected results:
the consumption should stay pretty much the same
Additional info:
This is not easily reproducable, but apart from running many requests and
watching the consumption grow, a quicker, but more involved way might be to
check with the gdb that no tevent_req structures are allocated on top of the
rctx after a request finishes. Please let me know which approach is preferable
for QE.