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

investigate duplicate rename events from mount namespace #73

Closed
fntlnz opened this issue Feb 4, 2022 · 1 comment · Fixed by #96
Closed

investigate duplicate rename events from mount namespace #73

fntlnz opened this issue Feb 4, 2022 · 1 comment · Fixed by #96
Assignees
Labels
v8.2.0 v8.2.0

Comments

@fntlnz
Copy link
Contributor

fntlnz commented Feb 4, 2022

I've been reading in #70 that we are rightfully concerned about how our File probes are behaving when reporting paths related to an overlay filesystem (container filesystem, non root mount namespace)

I talked with @ferullo and he confirmed that the requirement for "step 1" is to always report the path as it is in the root mount namespace.

In certain circumstances, it could happen that an event is duplicated (e.g: we see both the unlink event in the container mount namespace and in the root mount namespace)

We need to make sure that for file create, rename and delete we only report the root mount namespace events.

@qcorporation
Copy link

ping @rhysre before working on

@tabell tabell changed the title File events: make sure that the reported paths are the ones on root mount namespace duplicate rename events from mount namespace Apr 4, 2022
@tabell tabell changed the title duplicate rename events from mount namespace investigate duplicate rename events from mount namespace Apr 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v8.2.0 v8.2.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants