From owner-freebsd-hackers Fri Jan 12 11:39:20 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 2D00C37B401; Fri, 12 Jan 2001 11:39:02 -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 ; Fri, 12 Jan 2001 13:39:05 -0600 (CST) Message-ID: <006601c07cd0$1063ed80$edcf1f40@pdq.net> From: "Jason Smethers" To: "John Baldwin" Cc: References: Subject: Re: Mutexs: checking for initialization Date: Fri, 12 Jan 2001 13:44:22 -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 From: "John Baldwin" > Umm, well, you could write a function that walked the all_mtx list and checked > if the mutex was in that list. However, I think that you are using the wrong > tool for your problem here. :) I'm not sure validating mutexes is the way to > validate all the data you are receiving. We'll, I'm not validating ALL the data with the mutic, just the mutic itself. Anyway, after sleep and a shower I come back and have a 'Duh' moment. What am I trying to do and what am I doing? If I can't trust the data being passed, how can I trust the memory it's in. Time to change the model to a one time memory copy hit. =) Thanks - Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message