Skip to content
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

Remove fanotify warning on ubuntu pro fsmonitor initialisation #14156

Merged
merged 3 commits into from
Sep 26, 2024

Conversation

markylaing
Copy link
Contributor

This change allows the caller to specify a driver when loading an fsmonitor, or they can specify "any" to try to load fanotify but fallback to inotify if it fails.

@markylaing markylaing added the Bug Confirmed to be a bug label Sep 25, 2024
@markylaing markylaing self-assigned this Sep 25, 2024
Copy link
Member

@tomponline tomponline left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason we cant handle this logic inside fsmonitor itself by detecting if the path being monitored is a mount path (using filesystem.IsMountPoint) and only trying inotify if its not a mount point, rather than expanding the API and putting the burden on the caller to work it out?

@markylaing
Copy link
Contributor Author

Is there a reason we cant handle this logic inside fsmonitor itself by detecting if the path being monitored is a mount path (using filesystem.IsMountPoint) and only trying inotify if its not a mount point, rather than expanding the API and putting the burden on the caller to work it out?

Nope. I just didn't think of that... Will change.

Signed-off-by: Mark Laing <mark.laing@canonical.com>
Signed-off-by: Mark Laing <mark.laing@canonical.com>
… mount point.

Signed-off-by: Mark Laing <mark.laing@canonical.com>
@tomponline tomponline merged commit 2aad04d into canonical:main Sep 26, 2024
30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Confirmed to be a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants