An error occurred fetching the project authors.
- 07 Apr, 2023 2 commits
-
-
Han-Wen Nienhuys authored
Change-Id: I9357f137487d1c958a95ed46db081b7775604b6b
-
Han-Wen Nienhuys authored
Change-Id: I115ebce34aaf22767bb8b90b842927c133e30b65
-
- 30 Jan, 2023 1 commit
-
-
Jakob Unterwurzacher authored
Reason for adding DirectMountStrict is making the DirectMount functionality testable, though it may have value for the user in some cases. Add defaultRawFileSystem & loopback tests for DirectMount and DirectMountStrict. The tests fail right now due to bugs in DirectMount that will be fixed shortly: go-fuse/fuse$ sudo /usr/local/go/bin/go test -run TestDirectMount [...] 2022/12/28 20:19:21 mountDirect: calling syscall.Mount("", "/tmp/TestDirectMount3242971772", "fuse./tmp/go-build1215740", 0x0, "fd=7,rootmode=40000,user_id=0,group_id=0") 2022/12/28 20:19:21 mount: failed to do direct mount: invalid argument [...] Change-Id: Ibfa2fa141cb43e1f8c7319233c454a3e85fa435e
-
- 11 Jan, 2022 1 commit
-
-
hotaery authored
Change-Id: I7b8d1a6be288324021c846273aceb08eb9010e98
-
- 18 Jul, 2020 1 commit
-
-
Jakob Unterwurzacher authored
Also add a test if "ro" works directly in the fs package. Currently fails like this (will be fixed later): --- FAIL: TestRoMount (0.01s) simple_test.go:116: read-only file syste Change-Id: I8194360b1d092268784b9c2b17de274b86633aa2
-
- 03 Jan, 2020 1 commit
-
-
Jakob Unterwurzacher authored
Stop following symlinks when working with extended attributes, and add a test for it. Problem found by xfstests generic/062. Change-Id: I67f94451322cdfebdcbcc3af21679ccd4e2800d7
-
- 26 Nov, 2019 1 commit
-
-
Jakob Unterwurzacher authored
ListXAttr called with an empty buffer returns the current size of the list but does not touch the buffer (see man 2 listxattr). Fixes the xfstests generic/020 crash. Fixes https://github.com/hanwen/go-fuse/issues/337 . Add test Co-authored-by: Han-Wen Nienhuys <hanwen@google.com> Change-Id: I94c94bc56fdf506d2eb924b246336b787fa2976a
-
- 02 Aug, 2019 1 commit
-
-
Han-Wen Nienhuys authored
Change-Id: I811c6a070bfdc3582da816f302354f4a7516beab
-
- 17 Apr, 2019 1 commit
-
-
Han-Wen Nienhuys authored
The new naming makes clear that this is the One True API for Go-FUSE
-
- 16 Apr, 2019 1 commit
-
-
Jakob Unterwurzacher authored
There is a hang that appears when enabling CAP_PARALLEL_DIROPS on Linux 4.15.0: https://github.com/hanwen/go-fuse/issues/281 The hang was originally triggered by gvfs-udisks2-volume-monitor. This test emulates what gvfs-udisks2-volume-monitor does. On 4.15.0 kernels, the test will get stuck, and after 120 seconds you get a kernel backtrace like this: [ 1813.463679] INFO: task nodefs.test:2357 blocked for more than 120 seconds. [ 1813.463685] Not tainted 4.15.0-45-generic #48~16.04.1-Ubuntu [ 1813.463687] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1813.463689] nodefs.test D 0 2357 2311 0x00000004 [ 1813.463691] Call Trace: [ 1813.463709] __schedule+0x3d6/0x8b0 [ 1813.463712] schedule+0x36/0x80 [ 1813.463714] schedule_preempt_disabled+0xe/0x10 [ 1813.463716] __mutex_lock.isra.2+0x2ae/0x4e0 [ 1813.463720] ? ___slab_alloc+0x223/0x4e0 [ 1813.463722] ? _cond_resched+0x1a/0x50 [ 1813.463724] __mutex_lock_slowpath+0x13/0x20 [ 1813.463725] ? __mutex_lock_slowpath+0x13/0x20 [ 1813.463727] mutex_lock+0x2f/0x40 [ 1813.463729] fuse_lock_inode+0x2a/0x30 [ 1813.463732] fuse_lookup+0x31/0x140 [ 1813.463735] ? d_alloc_parallel+0xc1/0x4c0 [ 1813.463738] fuse_atomic_open+0x6d/0xf0 [ 1813.463740] path_openat+0xc5d/0x13f0 [ 1813.463744] do_filp_open+0x99/0x110 [ 1813.463747] ? __check_object_size+0xfc/0x1a0 [ 1813.463749] ? __alloc_fd+0x46/0x170 [ 1813.463752] do_sys_open+0x12d/0x290 [ 1813.463754] ? do_sys_open+0x12d/0x290 [ 1813.463756] SyS_openat+0x14/0x20 [ 1813.463759] do_syscall_64+0x73/0x130 [ 1813.463762] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
-
- 09 Apr, 2019 1 commit
-
-
Han-Wen Nienhuys authored
This reduces the debug output from 25k lines to ~1k
-
- 06 Apr, 2019 1 commit
-
-
Han-Wen Nienhuys authored
-
- 27 Mar, 2019 2 commits
-
-
Han-Wen Nienhuys authored
syscall.Close is not safe to run twice. Reused fds cause random things to break.
-
Han-Wen Nienhuys authored
-