Re: kern/49171: panic when closing a pty

[Alan Barrett <apb%cequrux.com@localhost>]

Here's another instance of the same or a related problem.
Sources checked out from CVS with -D '2014-09-26 00:00 UTC'.

The panic message is:

kernel diagnostic assertion "node != NULL" failed: file "src/sys/kern/vfs_vnode.c", line 1426

The backtrace is:

#10 0xc08b9f40 in vpanic (
   fmt=fmt@entry=0xc0cca854 "kernel %sassertion \"%s\" failed: file \"%s\", line %d ",
   ap=ap@entry=0xdda78d9c "\005\252\314\300\031\304\314\300Hn�\300\222\005")
   at src/sys/kern/subr_prf.c:338
#11 0xc0a6b604 in kern_assert (
   fmt=fmt@entry=0xc0cca854 "kernel %sassertion \"%s\" failed: file \"%s\", line %d ")
   at src/sys/lib/libkern/kern_assert.c:51
#12 0xc09e782e in vcache_remove (mp=0x0, key=0xc789a478, key_len=8)
   at src/sys/kern/vfs_vnode.c:1426
#13 0xc07d3e7e in ptyfs_reclaim (v=0xdda78dfc)
   at src/sys/fs/ptyfs/ptyfs_vnops.c:228
#14 0xc0a01367 in VOP_RECLAIM (vp=vp@entry=0xcc37fdc4)
   at src/sys/kern/vnode_if.c:1136
#15 0xc09e496d in vclean (vp=vp@entry=0xcc37fdc4)
   at src/sys/kern/vfs_vnode.c:1032
#16 0xc09e6b0b in vgone (vp=0xcc37fdc4)
   at src/sys/kern/vfs_vnode.c:1145
#17 0xc09e6bae in vrevoke (vp=0xcc33d218)
   at src/sys/kern/vfs_vnode.c:1129
#18 0xc036ec3f in genfs_revoke (v=0xdda78ea0)
   at src/sys/miscfs/genfs/genfs_vnops.c:276
#19 0xc0a00c67 in VOP_REVOKE (vp=vp@entry=0xcc33d218, flags=flags@entry=1)
   at src/sys/kern/vnode_if.c:656
#20 0xc0638173 in exit1 (l=l@entry=0xd0c44a80, rv=0)
   at src/sys/kern/kern_exit.c:395
#21 0xc0638473 in sys_exit (l=0xd0c44a80, uap=0xdda78f68, retval=0xdda78f60)
   at src/sys/kern/kern_exit.c:181
#22 0xc08dc743 in sy_call (rval=0xdda78f60, uap=0xdda78f68, l=0xd0c44a80,
   sy=<optimized out>) at src/sys/sys/syscallvar.h:61
#23 sy_invoke (code=1, rval=0xdda78f60, uap=0xdda78f68, l=0xd0c44a80,
   sy=<optimized out>) at src/sys/sys/syscallvar.h:85
#24 syscall (frame=0xdda78fa8)
   at src/sys/arch/x86/x86/syscall.c:156
#25 0xc01005c6 in Xsyscall ()
#26 0xdda78fa8 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)