Fix kmscon using 100% CPU when trying to read systemd seats configuration#157
Merged
Fix kmscon using 100% CPU when trying to read systemd seats configuration#157
Conversation
When selinux prevents kmscon to read from systemd socket, kmscon uses 100% CPU, because its epoll loop has always a read event on systemd socket, that cannot be cleared. So remove the fd from the epoll loop, if read returns an error. Signed-off-by: Jocelyn Falempe <[email protected]>
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
1 participant
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 selinux prevents kmscon to read from systemd socket, kmscon uses 100% CPU, because its epoll loop has always a read event on systemd socket, that cannot be cleared.
So remove the fd from the epoll loop, if read returns an error.