The Samba-Bugzilla – Bug 13290
A disconnecting winbind client can cause a problem in the winbind parent child communication
Last modified: 2018-03-22 20:50:30 UTC
When disconnect a winbind client with a pending request, all memory related
to that request is destroyed, which makes it impossible to keep the
winbind parent child communication working, so we have to abandon the child.
Instead we should keep some state and wait for the child to finish the request
and continue from there.
We have seen customer setups with many abandoned winbindd child processes,
all consuming memory and cpu. We already have a working timeout checking
in the parent child communication, is a child really becomes unusable.
Created attachment 13997 [details]
Patch for 4.8 cherry-picked from master
Pushed to autobuild-v4-8-test. But needs backport to older versions.
(In reply to Stefan Metzmacher from comment #2)
Pushed to v4-8-test.
Re-assigning to Metze for backports.