Skip to content

Conversation

@danielocfb
Copy link
Collaborator

Evidently, some file systems require write permissions in order to lock a file or locking will fail. Open the README file, which we use for locking purposes, with write permissions in an attempt to make locking work on all file systems that the crate may be built on.

Closes: #116

Evidently, some file systems require write permissions in order to lock
a file or locking will fail. Open the README file, which we use for
locking purposes, with write permissions in an attempt to make locking
work on all file systems that the crate may be built on.

Closes: libbpf#116

Signed-off-by: Daniel Müller <[email protected]>
@danielocfb
Copy link
Collaborator Author

I guess this could potentially blow up on a read-only file system, which also isn't great...

@danielocfb
Copy link
Collaborator Author

I guess this could potentially blow up on a read-only file system, which also isn't great...

Added a fallback now.

@danielocfb danielocfb merged commit 3992fe7 into libbpf:master May 1, 2025
11 checks passed
@danielocfb danielocfb deleted the topic/flock branch May 1, 2025 16:35
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

Successfully merging this pull request may close these issues.

flock in compiling vendoring libraries failed for NFS

2 participants