On Sun, Feb 22, 2015 at 03:00:25PM -0800, Sean Bruno wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> On 02/22/15 10:54, Sean Bruno wrote:
> > On 02/22/15 10:53, Konstantin Belousov wrote:
> >> On Sun, Feb 22, 2015 at 10:46:53AM -0800, Sean Bruno wrote:
> >>> Hmm ... looks unrelated to signals (maybe).  This looks like a 
> >>> common ZFS deadlock that is yet undiagnosed.  I do not have a 
> >>> show alllocks command available in db> .  I will show each
> >>> lock information below:
> >> Add witness.
> > 
> >>> 
> >>> db> show lockedvnods Locked vnodes
> >>> 
> >>> 0xfffff801141a6588: tag zfs, type VDIR usecount 19, writecount
> >>> 0, refcount 20 mountedhere 0 flags (VV_ROOT|VI_ACTIVE)
> >>> v_object 0xfffff80079be4500 ref 0 pages 0 cleanbuf 0 dirtybuf 0
> >>> lock type zfs: EXCL by thread 0xfffff801ca10c4a0 (pid 75907,
> >>> sh, tid 101262) with exclusive waiters pending
> >> Without backtraces of the acquisition, it is not useful.  You
> >> need DEBUG_VFS_LOCKS for this.
> > 
> > 
> > 
> > Thank you.  I will do so and restart my non-determinstic test and
> > see what I can find.
> > 
> > sean _______________________
> 
> Well, that was certainly enlightening.  I was able to get a WITNESS
> panic in imgact_binmisc.c in an hour or two.  I need to *not* hold the
> mtx protecting the list of activators over the bcopy in
> imgact_binmisc_exec().
> 
> Jiles proposes that we switch to an sx lock here for simplicity of
> change of the code.
> Kernel page fault with the following non-sleepable locks held:
> exclusive sleep mutex imgact_binmisc (imgact_binmisc) r = 0
> (0xffffffff82012418) locked @
> /usr/src/sys/modules/imgact_binmisc/../../kern/imgact_binmisc.c:596

So was it the reason for your troubles after the patch for handling
core file' vnode refcount properly ?  Or is there something more left ?
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to