Summary: | unionfs or tmpfs kernel panic | ||
---|---|---|---|
Product: | Base System | Reporter: | Shawn Webb <shawn.webb> |
Component: | kern | Assignee: | freebsd-fs (Nobody) <fs> |
Status: | New --- | ||
Severity: | Affects Only Me | CC: | agh, bdrewery, emaste, franco, mqudsi |
Priority: | --- | ||
Version: | 10.2-BETA1 | ||
Hardware: | Any | ||
OS: | Any |
Description
Shawn Webb
2015-07-18 16:37:25 UTC
This ought to fix it: https://github.com/opnsense/src/commit/d9cb17f050e083 I was reluctant to file a PR because I couldn't reproduce on a vanilla FreeBSD. Note the fix is from March. Need to pick this back up. Would like to see this brought into in 11-CURRENT if there are no objections? (In reply to Franco Fichtner from comment #1) tmpfs change is completely wrong, there is no reason for tmpfs vnode lock to be recursive. Unionfs is broken architecturally, it was so for the whole its existence, which is cause of this backtrace and many other issues you could get with the unionfs breaking all assumptions of VFS and filesystems. Cool, what is the proposed workaround or replacement in this case? :) (In reply to Franco Fichtner from comment #4) > Cool, what is the proposed workaround or replacement in this case? :) As Kib pointed out, Unionfs is plain broken. I know of some people who are hacking on it in their spare time, but I don't expect it to be fixed any time soon. So, to wrap this up, I have this one last question: Are there any bad side effects from using this patch as a workaround? Thanks in advance, Franco |