From owner-freebsd-hackers Thu Jan 11 20:16: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.iadfw.net (mail2.iadfw.net [206.66.12.234]) by hub.freebsd.org (Postfix) with SMTP id 1DDFE37B401 for ; Thu, 11 Jan 2001 20:15:46 -0800 (PST) Received: from Jason from [64.31.207.237] by mail2.iadfw.net (/\##/\ Smail3.1.30.16 #30.27) with smtp for sender: id ; Thu, 11 Jan 2001 21:56:31 -0600 (CST) Message-ID: <00a701c07c4c$61db61e0$edcf1f40@pdq.net> From: "Jason Smethers" To: Subject: Mutexs: checking for initialization Date: Thu, 11 Jan 2001 22:01:46 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got some kernel code that passes untrusted data containing mutic. I'd like to be able to check if the mutic have been initialized and return an error if they haven't. As of now I don't see a standard way of checking for initialization. I'd like to do it this way to abstract out the way things are locked, and in FreeBSD's case the mutex's description. I known I can do this other ways, but it'd be nice if there was a standard way to check for this. Just a thought, or else I'd have a diff =O. Thanks - Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message