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
Restrict error handling of readahead #3305
Restrict error handling of readahead #3305
Conversation
@cernvm-bot cloudtest |
building for cloudtests finished: SUCCESS |
cloudtests finished: FAILURE |
cannot reproduce the failure of |
@cernvm-bot cloudtest |
building for cloudtests finished: UNSTABLE |
@cernvm-bot cloudtest |
building for cloudtests finished: SUCCESS |
cloudtests finished: FAILURE |
@cernvm-bot cloudtest |
building for cloudtests finished: SUCCESS |
cloudtests finished: FAILURE |
fd5b72c
to
8c7a5f7
Compare
@cernvm-bot cloudtest |
building for cloudtests finished: SUCCESS |
cloudtests finished: FAILURE |
@cernvm-bot cloudtest |
building for cloudtests finished: SUCCESS |
cloudtests finished: SUCCESS |
Issue #3299
Instead of just removing
kLogSyslogWarn
, i think it is better to ignore errors due to not supported file type but have a hard failure if the readahead() fails due toEBADF fd is not a valid file descriptor or is not open for reading.
Man page says the on error only errnos set are either
EBADF
andEINVAL