Deadlock when multiple MacFUSE file systems are mounted #10
Milestone
Comments
bfleischer
added a commit
that referenced
this issue
Sep 6, 2011
… time a MacFUSE file system is mounted When a MacFUSE file system is mounted the sysctl "osxfuse.control.macfuse_mode" is set to 1. Each time that happens the kernel extension registers MacFUSE's sysctls. Registering already registered sysctls triggers a deadlock. Closes issue #10: Deadlock when multiple MacFUSE file systems are mounted
bfleischer
added a commit
that referenced
this issue
Nov 4, 2011
… time a MacFUSE file system is mounted When a MacFUSE file system is mounted the sysctl "osxfuse.control.macfuse_mode" is set to 1. Each time that happens the kernel extension registers MacFUSE's sysctls. Registering already registered sysctls triggers a deadlock. Closes issue #10: Deadlock when multiple MacFUSE file systems are mounted
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a MacFUSE file system is mounted the sysctl "osxfuse.control.macfuse_mode" is set to 1. Each time that happens the kernel extension registers MacFUSE's sysctls. Registering already registered sysctls triggers a system-wide deadlock.
This only affects MacFUSE file systems linked against libfuse or libfuse_ino64. Objective-C file systems using MacFUSE.framework do not trigger the deadlock.
Reported by @PeterStegemann and @unsound
The text was updated successfully, but these errors were encountered: