hardcoresushi/libgocryptfs
1
0
Fork 0
Code Issues Pull Requests Releases Activity

mount: set DirectMount: true

Browse Source 
Attempt to directly call mount(2) before trying fusermount. This means we
can do without fusermount if running as root.

https://github.com/rfjakob/gocryptfs/issues/697
This commit is contained in:
Jakob Unterwurzacher 2023-05-17 16:47:22 +02:00
parent 8d3b992824
commit a40e9a8622
2 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -195,6 +195,11 @@ RM: 2,367
Changelog Changelog
--------- ---------
#### vNEXT, in progress
* Attempt to directly call mount(2) before trying fusermount. This means we
can do without fusermount if running as root or in a root-like namespace
([#697](https://github.com/rfjakob/gocryptfs/issues/697)).
#### v2.3.2, 2023-04-29 #### v2.3.2, 2023-04-29
* Fix incorrect file size reported after hard link creation * Fix incorrect file size reported after hard link creation
([#724](https://github.com/rfjakob/gocryptfs/issues/724)) ([#724](https://github.com/rfjakob/gocryptfs/issues/724))

3
mount.go
View File

@ -396,6 +396,9 @@ func initGoFuse(rootNode fs.InodeEmbedder, args *argContainer) *fuse.Server {
// Setting SyncRead disables FUSE_CAP_ASYNC_READ. This makes the kernel // Setting SyncRead disables FUSE_CAP_ASYNC_READ. This makes the kernel
// do everything in-order without parallelism. // do everything in-order without parallelism.
SyncRead: args.serialize_reads, SyncRead: args.serialize_reads,
// Attempt to directly call mount(2) before trying fusermount. This means we
// can do without fusermount if running as root.
DirectMount: true,
} }
mOpts := &fuseOpts.MountOptions mOpts := &fuseOpts.MountOptions