Date: Thu, 14 Apr 2016 12:15:14 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Message-ID: <bug-204426-16-YlQO2NU57K@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-204426-16@https.bugs.freebsd.org/bugzilla/> References: <bug-204426-16@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #90 from Robert Blayzor <rblayzor@inoc.net> --- In 12 days of running since the last debug patch, I've seen only the below = on a couple of the VM's.... lock order reversal: 1st 0xfffff80009e5c418 ufs (ufs) @ /.amd_mnt/juno/pub/FreeBSD/10-STABLE/sys/kern/vfs_subr.c:2253 2nd 0xfffffe007c5c37f8 bufwait (bufwait) @ /.amd_mnt/juno/pub/FreeBSD/10-STABLE/sys/ufs/ffs/ffs_vnops.c:262 3rd 0xfffff80064499418 ufs (ufs) @ /.amd_mnt/juno/pub/FreeBSD/10-STABLE/sys/kern/vfs_subr.c:2253 KDB: stack backtrace: #0 0xffffffff80484260 at kdb_backtrace+0x60 #1 0xffffffff804a30d4 at witness_checkorder+0xe24 #2 0xffffffff8042b98a at __lockmgr_args+0x9ea #3 0xffffffff806818f4 at ffs_lock+0x84 #4 0xffffffff8073dc2c at VOP_LOCK1_APV+0xfc #5 0xffffffff805057da at _vn_lock+0xaa #6 0xffffffff804f6de7 at vget+0x67 #7 0xffffffff804ea601 at vfs_hash_get+0xe1 #8 0xffffffff8067cf00 at ffs_vgetf+0x40 #9 0xffffffff80674bf0 at softdep_sync_buf+0xac0 #10 0xffffffff80682656 at ffs_syncvnode+0x286 #11 0xffffffff80659a5e at ffs_truncate+0x6ae #12 0xffffffff8068987a at ufs_direnter+0x81a #13 0xffffffff806926a5 at ufs_makeinode+0x575 #14 0xffffffff8068e58d at ufs_create+0x2d #15 0xffffffff8073b5c1 at VOP_CREATE_APV+0xf1 #16 0xffffffff80504e93 at vn_open_cred+0x2c3 #17 0xffffffff804fdf8f at kern_openat+0x26f --=20 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-204426-16-YlQO2NU57K>