Open
Conversation
When running libnss-cache behind nscd, this author observed a large number of fd leaks that corresponded to cache files. In the scenario in which the leaks occurred, the leaked fds prevented old deleted cache files from getting freed on disk, and resulted in the root volume filling up. An audit of the nss_cache module found multiple paths where it was possible to leak a FILE pointer that would in turn result in a fd being leaked. After applying this fix, none of the leaks reoccurred, even after 24+ hours of testing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When running libnss-cache behind nscd, this author observed fd leaks that corresponded to cache files. In the scenario in which the leaks occurred, the leaked fds prevented old deleted cache files from getting freed on disk, and resulted in the root volume filling up.
An audit of the nss_cache module found multiple paths where it was possible to leak a FILE pointer that would in turn result in a fd being leaked. After applying this fix, none of the leaks reoccurred, even after 24+ hours of testing.
For the changes outside of
_nss_cache_bsearch2, the fix mimics the behavior in the internal glibc functions. E.g. if the FILE pointer is NULL, open the file. Otherwise, rewind the FILE.