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

enable CONFIG_FANOTIFY_ACCESS_PERMISSIONS #3941

Open
Tracked by #1604
alban opened this issue Jul 13, 2023 · 0 comments
Open
Tracked by #1604

enable CONFIG_FANOTIFY_ACCESS_PERMISSIONS #3941

alban opened this issue Jul 13, 2023 · 0 comments

Comments

@alban
Copy link

alban commented Jul 13, 2023

Description

The kernel is compiled without CONFIG_FANOTIFY_ACCESS_PERMISSIONS:

CONFIG_FANOTIFY=y
# CONFIG_FANOTIFY_ACCESS_PERMISSIONS is not set

Unfortunately, my software needs both CONFIG_FANOTIFY and CONFIG_FANOTIFY_ACCESS_PERMISSIONS.

This results in the following error when using the fanotify_mark syscall with with FAN_ACCESS_PERM or FAN_OPEN_EXEC_PERM flags:

failed to fanotify mark: fanotify: mark error, invalid argument

Steps to reproduce the issue:

Run ig as explained in the instructions:

$ docker run -ti --rm --privileged -v /run:/run -v /:/host ghcr.io/inspektor-gadget/ig list-containers --auto-mount-filesystems
failed to fanotify mark: fanotify: mark error, invalid argument

Describe the results you received:

fanotify_mark syscall with FAN_ACCESS_PERM and FAN_OPEN_EXEC_PERM should work fine.

Describe the results you expected:

fanotify_mark syscall with FAN_ACCESS_PERM and FAN_OPEN_EXEC_PERM should work fine.

Additional information you deem important (e.g. issue happens only occasionally):

docker/for-mac#6915

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant