NetBSD Problem Report #41251

From yamt@mwd.biglobe.ne.jp  Mon Apr 20 01:07:11 2009
Return-Path: <yamt@mwd.biglobe.ne.jp>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id 5AD8C63C1FA
	for <gnats-bugs@gnats.NetBSD.org>; Mon, 20 Apr 2009 01:07:11 +0000 (UTC)
Message-Id: <20090419234752.4F5A197EF8@kaeru.lan>
Date: Mon, 20 Apr 2009 08:47:52 +0900 (JST)
From: yamt@mwd.biglobe.ne.jp
Reply-To: yamt@mwd.biglobe.ne.jp
To: gnats-bugs@gnats.NetBSD.org
Subject: veriexec locking seems broken
X-Send-Pr-Version: 3.95

>Number:         41251
>Category:       kern
>Synopsis:       veriexec locking seems broken
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 20 01:10:00 +0000 2009
>Originator:     YAMAMOTO Takashi <yamt@mwd.biglobe.ne.jp>
>Release:        NetBSD 5.99.11
>Organization:

>Environment:


System: NetBSD kaeru 5.99.11
Architecture: i386
Machine: i386
>Description:
	locking seems broken in veriexec.

	- VERIEXEC_RW_UPGRADE is something unacceptable.
	- veriexec_fp_calc seems to be confused and mix vnode lock and
	  veriexec_op_lock.
	- it traverses mountlist without locking.
>How-To-Repeat:
	code inspection.
>Fix:


>Unformatted:

Home	PR Database Search