Date: Thu, 01 Oct 2015 20:49:23 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 203492] mount_unionfs -o below causes panic Message-ID: <bug-203492-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203492 Bug ID: 203492 Summary: mount_unionfs -o below causes panic Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: mwlucas@michaelwlucas.com Created attachment 161624 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=161624&action=edit core.txt Running: FreeBSD storm 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r288449: Thu Oct 1 10:07:03 EDT 2015 root@storm:/usr/obj/usr/src/sys/JAIL amd64 The kernel config is: include GENERIC ident VIMAGE options VIMAGE options RACCT options RCTL The same behavior also occurs on GENERIC, however. This host has a jails pool, with two datasets: basejail and jail1. I want jail1 to be the mountpoint, and mount jail1 on top of basejail. My understanding is that I can then reuse the basejail dataset for multiple jails. # cd jails # mount_unionfs -o below basejail/ jail1/ If I go into /jails/jail1 and try to remove something from the lower layer, I get a panic. Unread portion of the kernel message buffer: panic: solaris assert: cnp->cn_namelen < sizeof(nm), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: 6213 cpuid = 3 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe085d12b360 vpanic() at vpanic+0x189/frame 0xfffffe085d12b3e0 panic() at panic+0x43/frame 0xfffffe085d12b440 assfail() at assfail+0x1a/frame 0xfffffe085d12b450 zfs_freebsd_lookup() at zfs_freebsd_lookup+0x47/frame 0xfffffe085d12b590 VOP_CACHEDLOOKUP_APV() at VOP_CACHEDLOOKUP_APV+0xf1/frame 0xfffffe085d12b5c0 vfs_cache_lookup() at vfs_cache_lookup+0xd6/frame 0xfffffe085d12b620 VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xf1/frame 0xfffffe085d12b650 relookup() at relookup+0xa1/frame 0xfffffe085d12b6b0 unionfs_relookup() at unionfs_relookup+0x105/frame 0xfffffe085d12b710 unionfs_relookup_for_delete() at unionfs_relookup_for_delete+0x56/frame 0xfffffe085d12b7a0 unionfs_rmdir() at unionfs_rmdir+0xd1/frame 0xfffffe085d12b800 VOP_RMDIR_APV() at VOP_RMDIR_APV+0xf7/frame 0xfffffe085d12b830 kern_rmdirat() at kern_rmdirat+0x1bc/frame 0xfffffe085d12b9a0 amd64_syscall() at amd64_syscall+0x2e1/frame 0xfffffe085d12bab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe085d12bab0 --- syscall (137, FreeBSD ELF64, sys_rmdir), rip = 0x800896dba, rsp = 0x7fffffffe8f8, rbp = 0x7fffffffe930 --- KDB: enter: panic -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203492-8>