NetBSD Problem Report #44094

From rmind@NetBSD.org  Mon Nov 15 15:35:50 2010
Return-Path: <rmind@NetBSD.org>
Received: by www.NetBSD.org (Postfix, from userid 1391)
	id E1B4563BA50; Mon, 15 Nov 2010 15:35:50 +0000 (UTC)
Message-Id: <20101115153550.E1B4563BA50@www.NetBSD.org>
Date: Mon, 15 Nov 2010 15:35:50 +0000 (UTC)
From: rmind@netbsd.org
Reply-To: rmind@netbsd.org
To: gnats-bugs@NetBSD.org
Subject: proplib has redundant locking
X-Send-Pr-Version: 3.95

>Number:         44094
>Category:       kern
>Synopsis:       proplib has redundant locking
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Nov 15 15:40:00 +0000 2010
>Originator:     Mindaugas Rasiukevicius
>Release:        NetBSD 5.99.39
>Organization:
The NetBSD Project
>Environment:
>Description:
	proplib(3) has internal locking and is MP-safe.  However, typical
	user of interface either (a) uses it in a single-threaded manner
	(b) needs to perform its own synchronisation and therefore provide
	locking at upper, caller's level.

	Note that interface parts which might block (e.g. allocate memory)
	should be documented for consideration of locking strategy and/or
	determinism.
>How-To-Repeat:
	Code inspection.
>Fix:
	Consider removal of locking from proplib(3).

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.