You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way hardlinks copies linked files does not work when the file is not readable.
This was tested with 1.6.
The use case covers unpacking cpio files and install rpm files, when there are linked files. Linked files in packages are quite common, specially in toolchain packages.
chmod 0755 /a
chmod: changing permissions of '/a': Permission denied
The reason is that the fuse fs wants to copy /a. But it is not readable.
At no point did hardlinks have any reason to copy /a, because the file is safe as it does not link to the read only file.
Possible fixes
Before copying a file with multiple links, we should make sure whether this file is safe. If it is, there is no reason to copy it. One way to know if a file is safe could be to add a special extended attribute to it.
Other relevant information
BuildStream version affected: /milestone %"BuildStream_v1.6"
The text was updated successfully, but these errors were encountered:
See original issue on GitLab
In GitLab by [Gitlab user @valentindavid] on Oct 2, 2020, 09:22
Summary
The way hardlinks copies linked files does not work when the file is not readable.
This was tested with 1.6.
The use case covers unpacking cpio files and install rpm files, when there are linked files. Linked files in packages are quite common, specially in toolchain packages.
Steps to reproduce
Consider the following:
This fails with:
The reason is that the fuse fs wants to copy
/a
. But it is not readable.At no point did hardlinks have any reason to copy
/a
, because the file is safe as it does not link to the read only file.Possible fixes
Before copying a file with multiple links, we should make sure whether this file is safe. If it is, there is no reason to copy it. One way to know if a file is safe could be to add a special extended attribute to it.
Other relevant information
The text was updated successfully, but these errors were encountered: