Re: kern/38646: -current panic with veriexec

[Pierre Pronchery <khorben%defora.org@localhost>]

The following reply was made to PR kern/38646; it has been noted by GNATS.

From: Pierre Pronchery <khorben%defora.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/38646: -current panic with veriexec
Date: Sat, 17 May 2008 17:54:36 +0200

 ascizo%fiveam.org@localhost wrote:
 >> Synopsis:       -current panic with veriexec
 >> Release:        NetBSD/i386 4.99.62 Thu May  8 09:18:09 EEST 2008
 
 Same here with NetBSD/sparc64 4.99.62, on a GENERIC kernel from moments
 before Fri May  9 00:11:51 CEST 2008.
 
 >> Description:
 > Reader / writer lock error: rw_vector_enter: locking against myself
 > 
 > lock address : 0x00000000cb37b130
 > current cpu  :                  0
 > current lwp  : 0x00000000ccdc8340
 > owner/count  : 0x00000000ccdc8340 flags:     0x0000000000000004
 > 
 > 
 > panic: lock error
 > Stopped in pid 383.1 (ls) at netbsd:breakpoint+0x4: popl %ebp
 > 
 > db{0}> bt
 > breakpoint()
 > panic()
 > lockdebug_abort()
 > rw_abort()
 > rw_vector_enter()
 > vlockmgr()
 > ffs_lock()
 > VOP_LOCK()
 > vn_lock()
 > vn_rdwr()
 > veriexec_fp_calc()
 > veriexex_file_verify()
 > veriexec_openchk()
 > vn_open()
 > sys_open()
 > syscall()
 
 Here is my stack trace:
 lockdebug_abort(c1b0b80, 181bca0, 14d9e18, 1632880, 0, dc081d8) at
 netbsd:lockdebug_abort+0x24
 rw_vector_enter(c1b0b80, 0, 0, 0, 0, d9c32c8) at
 netbsd:rw_vector_enter+0x130
 vlockmgr(c1b0b80, 1, d8da800, 0, 1, 0) at netbsd:vlockmgr+0xe4
 ffs_lock(d66e000, d9c352c, 2ea5840, ffffffffffffffff, 0, 2ced000) at
 netbsd:ffs_lock+0x48
 VOP_LOCK(c1b0aa0, 10001, ffffffffffffffff, 0, 0, dc0e000) at
 netbsd:VOP_LOCK+0x20
 vn_lock(c1b0aa0, 20001, 20, c9bfb60, 0, 0) at netbsd:vn_lock+0x9c
 vn_rdwr(0, c1b0aa0, dc0e000, 2000, 0, 1) at netbsd:vn_rdwr+0xfc
 veriexec_fp_calc(0, c1b0aa0, db65300, d93e6a0, 1, 0) at
 netbsd:veriexec_fp_calc+0xd4
 veriexec_file_verify(0, c1b0aa0, c1b7c00, 4, d93e6a0, 0) at
 netbsd:veriexec_file_verify+0x7c
 veriexec_openchk(d8da800, c1b0aa0, c1b7c00, 1, e, c1b7c00) at
 netbsd:veriexec_openchk+0x30
 vn_open(0, 1, d6d, ffffffffffffbad8, ffffffffffffbc20, ffffffffffffbc60)
 at netbsd:vn_open+0x118
 sys_open(0, d9c3dc0, d9c3e00, d9c3c28, 3, 1818a58) at netbsd:sys_open+0x90
 syscall_plain(d9c3ed0, 3, 4030b100, 4030b104, 0, d9c3dc0) at
 netbsd:syscall_plain+0x110
 ?(ffffffffffffb168, 0, 7f7f7f7f7f7f7f7f, fefefefefefefeff,
 ffffffffffffffff, ff00) at 0x1008c90
 
 >> How-To-Repeat:
 > veriexecctl load
 > [any command]
 
 I did this:
 # /etc/rc.d/veriexec onestart
 after running veriexecgen.
 
 I just finished to compile a -current kernel with LOCKDEBUG and will
 include the output in another reply.
 
 HTH,
 -- 
 khorben