From owner-freebsd-hackers Tue Sep 25 12:27:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 1D1CB37B40C for ; Tue, 25 Sep 2001 12:26:16 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f8PJOHW03718; Tue, 25 Sep 2001 12:24:17 -0700 (PDT) (envelope-from dillon) Date: Tue, 25 Sep 2001 12:24:17 -0700 (PDT) From: Matt Dillon Message-Id: <200109251924.f8PJOHW03718@earth.backplane.com> To: Mike Silbersack Cc: Ian Dowse , Subject: Re: VM Corruption - stumped, anyone have any ideas? References: <20010924213518.G70783-100000@achilles.silby.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Ok, time to take a good stab at sticking my foot in my mouth here. : :Would it be possible to have a kernel mode where the read-only bit was :turned on for malloc pools which shouldn't currently be accessed? This :could be gated through the spl() calls (or specific mutexes on -current), :ensuring that something like getpid couldn't stomp on the vm structures :w/o first doing a splvm(). Kinda sounds like Multics :-)... no, it would be too messy trying to protect kernel structures in one subsystem from another. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message