-
Notifications
You must be signed in to change notification settings - Fork 84
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
cp's copy_file_range vs read-only files #399
Comments
This is... shockingly fundamental to Lines 5409 to 5419 in 6452d53
|
I ran into this, and it is a fatal bug for my workflow. I am on an Ubuntu box, using default repositories $ fuse-overlayfs --version
fuse-overlayfs: version 1.7.1
FUSE library version 3.10.5
using FUSE kernel interface version 7.31
fusermount3 version: 3.10.5 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running the following straightforward sequence on a
fuse-overlayfs
mountbreaks thusly
and leaves behind a zero-byte file:
strace
-ing that failingcp
shows thatcopy_file_range
is failing:strace
-ingfuse-overlayfs
itself shows that it attempts to re-open the file rather than using the open handle it already has, resulting in different access semantics:The system running this is a pretty bog-standard Debian box, save that it's ppc64le, but that shouldn't matter here.
fuse-overlayfs
is their build of version 1.10.The text was updated successfully, but these errors were encountered: