Date: Wed, 22 Apr 1998 06:38:27 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: sfarrell+lists@farrell.org Cc: syssgm@dtir.qld.gov.au, freebsd-current@FreeBSD.ORG Subject: Re: panic: vm_page_free: freeing busy page Message-ID: <199804220638.XAA01355@usr06.primenet.com> In-Reply-To: <87n2dfp1e1.fsf@phaedrus.uchicago.edu> from "sfarrell%2Blists@farrell.org" at Apr 21, 98 11:47:50 am
next in thread | previous in thread | raw e-mail | index | archive | help
> Well, no, but I got a question: in freebsd current, what prevents the > kernel from reallocating a process' memory after it calls exit() and > before it is finished freeing its memory up? I'm reading in the > 4.4BSD book p. 155 that they raise the interrupt level, and I > understand that doesn't work for SMP. So presumably there is some new > mechanism for this in current? (which might be related to this > crash??) By definition, all tracked resources, with the exception of the proc struct, are freed by a process when exit(2) is called. Specifically, the proc struct is left around so the parent can "reap" the process using the "wait" family of calls. The status is reaped from the proc struct. Programs do not return from the exit(2) call. The meory may be reused. in general, this would be done because it's perfectly reasonable to reuse the memory, since it was freed. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199804220638.XAA01355>