From owner-freebsd-hackers Thu Mar 23 23:27:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A2F9237B56D for ; Thu, 23 Mar 2000 23:27:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA08899; Thu, 23 Mar 2000 23:27:46 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 23:27:46 -0800 (PST) From: Matthew Dillon Message-Id: <200003240727.XAA08899@apollo.backplane.com> To: Chad David Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vm_await() References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In vm_await(), asleep() is called with "vmwait", and then :vm_await() just returns. What then happens to the memory at :"vmwait" that was passed to asleep()? : :Am I missing something, other than vm_await is never called :so it doesn't really matter? : :Also, with a quick find, it looks like atapi_queue_cmd() does the :same thing in atapi-all.c, but I might be missing something here. : :Chad The memory at the 'wait' address you tsleep and wakeup on is never actually accessed, the address is simply used as a placemarker in the hash table. So it's ok to asleep() on an address and then never use it, and it's ok if the object represented by the address is ripped out from under you in that case. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message