From: Harald Hoyer <harald> At the start of auditd, we are temporarily not able to read from the fanotify fd. Ignoring it, seems to work. --- src/readahead-collect.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/readahead-collect.c b/src/readahead-collect.c index 3c48a02..913a340 100644 --- a/src/readahead-collect.c +++ b/src/readahead-collect.c @@ -380,7 +380,7 @@ static int collect(const char *root) { if ((n = read(fanotify_fd, &data, sizeof(data))) < 0) { - if (errno == EINTR || errno == EAGAIN) + if (errno == EINTR || errno == EAGAIN || errno == EACCES) continue; log_error("Failed to read event: %m");
ok, seems to be a kernel bug... reassigning.
I have no applied Harald's fix to work around the problem for now. It's also in F15.
Did this ever get worked on/fixed?
(In reply to comment #3) > Did this ever get worked on/fixed? Don't know.. might still be present
current systemd-readahead-collect works around the "bug" if ((n = read(fanotify_fd, &data, sizeof(data))) < 0) { if (errno == EINTR || errno == EAGAIN) continue; /* fanotify sometimes returns EACCES on read() * where it shouldn't. For now let's just * ignore it here (which is safe), but * eventually this should be * dropped when the kernel is fixed. * * https://bugzilla.redhat.com/show_bug.cgi?id=707577 */ if (errno == EACCES) continue; log_error("Failed to read event: %m"); r = -errno; goto finish; }
It's still there. Man I'm a bad maintainer.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Is this still an issue with the 3.9 kernels in F19?
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.