New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lazy setup of inotify_fd in sd-journal may cause clients to leak file descriptors #14695
Comments
msekletar
added a commit
to msekletar/systemd
that referenced
this issue
Feb 4, 2020
…we've setup inotify watch Fixes systemd#14695
msekletar
added a commit
to msekletar/systemd
that referenced
this issue
Feb 5, 2020
…we've setup inotify watch Fixes systemd#14695
keszybz
pushed a commit
that referenced
this issue
Feb 5, 2020
…we've setup inotify watch Fixes #14695
msekletar
added a commit
to msekletar/systemd
that referenced
this issue
Mar 27, 2020
journal_file_fstat() returns an error if we call it on already unlinked journal file and hence we never reach remove_file_real() which is the entire point. I must have made some mistake while testing the fix that got me thinking the issue is gone while opposite was true. Fixes systemd#14695
keszybz
pushed a commit
that referenced
this issue
Mar 28, 2020
journal_file_fstat() returns an error if we call it on already unlinked journal file and hence we never reach remove_file_real() which is the entire point. I must have made some mistake while testing the fix that got me thinking the issue is gone while opposite was true. Fixes #14695
DaanDeMeyer
pushed a commit
to DaanDeMeyer/systemd
that referenced
this issue
Mar 30, 2020
journal_file_fstat() returns an error if we call it on already unlinked journal file and hence we never reach remove_file_real() which is the entire point. I must have made some mistake while testing the fix that got me thinking the issue is gone while opposite was true. Fixes systemd#14695
eworm-de
pushed a commit
to eworm-de/systemd
that referenced
this issue
Jun 23, 2020
journal_file_fstat() returns an error if we call it on already unlinked journal file and hence we never reach remove_file_real() which is the entire point. I must have made some mistake while testing the fix that got me thinking the issue is gone while opposite was true. Fixes systemd#14695 (cherry picked from commit 8581b9f)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
systemd version the issue has been seen with
Used distribution
Expected behaviour you didn't see
sd_journal_process()Unexpected behaviour you saw
sd_journal_process(). This is because files were opened by the client and deleted by the server before we've setup inotify monitor.Steps to reproduce the problem
Example output of the reproducer script
The text was updated successfully, but these errors were encountered: