You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@buildstream.apache.org by GitBox <gi...@apache.org> on 2022/01/17 20:18:31 UTC

[GitHub] [buildstream] juergbi commented on pull request #1567: fuse/hardlinks: Do not follow symlinks for chown

juergbi commented on pull request #1567:
URL: https://github.com/apache/buildstream/pull/1567#issuecomment-1014860636


   > Is this not a problem for chmod?
   
   I indeed expect the same logic to be needed for `chmod` and `chown`.
   
   Actually, as I understand it, the low level (kernel) FUSE operations are all inode-based (to the extent possible) and libfuse maps inodes to paths to make it easier to implement (certain types of) filesystems. I.e., I would expect that we should never follow symlinks.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org