From fnaumann@mail.cs.uni-magdeburg.de Tue Jan 27 12:26:25 2004 X-Authentication-Warning: antyk.obta.uw.edu.pl: draco owned process doing -bs Date: Tue, 27 Jan 2004 12:15:03 +0100 (CET) From: "Konrad M. Kokoszkiewicz" To: mint@fishpool.com Subject: Re: [MiNT] fVDI issues In-Reply-To: Message-ID: <20040127121404.S43867@antyk.obta.uw.edu.pl> References: <20040122144133.GC17739@haddock.cd.chalmers.se> <00d401c3e198$9a156d80$0e0a63d9@blaszak> <20040123191858.GA28238@haddock.cd.chalmers.se> <20040124160439.GA24271@haddock.cd.chalmers.se> <035f01c3e333$a67d1b80$0e0a63d9@blaszak> <20040125124348.GA28027@haddock.cd.chalmers.se> <03d601c3e4af$aace91a0$0e0a63d9@blaszak> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: draco@obta.uw.edu.pl Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: > > Well, any writes/reads done by the CPU are controlled by the PMMU, > > right? So if the PMMU disallows the access, the program, that does the > > access, receives bus error signal. This is why you cannot Fread() a > > file and overwrite another process (other than the caller) this way. > > To say it again, it's a very, very bad idea to segfault inside the kernel. > That's very problematic for sure. Currently it is hardly avoidable, however. > > As far as I know, the kernel itself is currently unprotected at all. > > The text segment, not the allocated memory after the MMU management is > initialized. Exactly. Text, data and bss. CVV -- Konrad M.Kokoszkiewicz mail: draco@atari.org http://draco.atari.org ** Ea natura multitudinis est, ** aut servit humiliter, aut superbe dominatur (Liv. XXIV,25) ************************************************************* ** Taka to juz natura pospolstwa, ze albo sluzy ono unizenie, ** albo bezczelnie sie panoszy.