-
Notifications
You must be signed in to change notification settings - Fork 147
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
Ensure logs are committed to disk upon shutdown #2495
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #2495 +/- ##
============================================
- Coverage 78.71% 76.96% -1.75%
Complexity 267 267
============================================
Files 110 136 +26
Lines 13191 17008 +3817
Branches 0 897 +897
============================================
+ Hits 10383 13090 +2707
- Misses 2808 3467 +659
- Partials 0 451 +451
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 24 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
appsec/src/extension/logging.c
Outdated
int errno_fsync; | ||
int ret; | ||
do { | ||
fsync_ret = fsync(_mlog_fd); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you need to do fsync in the loop? Whether close
was interrupted has no bearing on the outcome of fsync
, although I guess it doesn't hurt either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah I guess i can move it out
Description
Reviewer checklist