Mac: Ensure that the kext blocks file I\O that that is not allowed when VFSForGit is unmounted
See original GitHub issueWe used to have this on Mac, but it had to be removed in #191 as it was preventing:
- VFS4G from modifying the .git/hooks a as part of mounting
gvfs repair
from being able to fix up files in the .git folder
As the feature is re-enabled we’ll need to consider how we can still support the scenarios above. Perhaps we can support a new xattr that VFS4G sets on folders letting the kext know that offline modifications are allowed? Or maybe there is some way that we can ACL/mark the VFS4G processes so that the kext knows that they should be allowed to make offline modifications?
Issue Analytics
- State:
- Created 5 years ago
- Comments:17 (17 by maintainers)
Top Results From Across the Web
Mac: Detect mode changes to placeholder files #457
Allow core.filemode to be configured by platform #590 ... Mac: Ensure that the kext blocks file I\O that that is not allowed when...
Read more >Accidentally Blocked a Kext and Can't Unblock It
I've been trying to install Intel Power Gadget on my macBook which requires loading a kernel extension. However, I accidentally clicked the ...
Read more >Alternative for Virtual file system (VFS) kernel extension on ...
we have developed a kernel extension (KEXT) for a virtual file system (VFS) on macOS to integrate our software with external programs like...
Read more >Where are the kext files? : r/hackintosh
In macOS, a kext appears as a file/container. In actuality, it's a folder with .kext on the end of the name, which is...
Read more >Using Git LFS and VFS for Git introduction
A solution to work with binary files is using Git LFS (or Git Large File System). This is an extension to Git and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@pmj thanks!
I think we can close this out.
Regarding this item:
I think we can stick with the current behavior and adjust it later if we get feedback that the current behavior is undesirable.
I’ve updated the description of #457 to include this work.
With #1429 done, there’s now not much left to do here. A few loose ends:
This is now implemented for empty files. I think that’s what we want: we already allow deleting files for other reasons than renaming, and I think it’s reasonable to allow a user to move hydrated or full files out of the repo, possibly in order to back up some work they did before deleting the repo entirely.
We do indeed get a callback with that action, or
KAUTH_VNODE_ADD_SUBDIRECTORY
if the thing being moved is a directory, and both are now blocked on offline roots as of #1429.I think this will be a case of blocking
KAUTH_VNODE_WRITE_SECURITY
when offline, but I’d have to check - and yes, I’d agree, let’s cover that as part of #457.