Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!ames!ucbcad!ucbvax!ucsfcgl!kneller
From: kneller@ucsfcgl.UUCP
Newsgroups: comp.os.minix
Subject: Re: MINIX memory management/protection
Message-ID: <10057@cgl.ucsf.edu.ucsfcgl.UUCP>
Date: Sat, 7-Feb-87 22:01:36 EST
Article-I.D.: cgl.10057
Posted: Sat Feb  7 22:01:36 1987
Date-Received: Sun, 8-Feb-87 08:31:32 EST
References: <252@hqda-ai.UUCP> <1169@steinmetz.steinmetz.UUCP> <511@bobkat.UUCP> <888@cartan.Berkeley.EDU> <299@netxcom.UUCP>
Sender: daemon@ucsfcgl.UUCP
Reply-To: kneller@cgl.ucsf.edu.UUCP (Don Kneller)
Organization: UCSF Computer Graphics Lab
Lines: 15
Keywords: shared swapped jobs
Summary: It's a joke, son.

In article <299@netxcom.UUCP> beattie@netxcom.UUCP (Brian Beattie) writes:
> [ ... ]
	Long discussion about getting out of your process by an
	errant return.
>
>Actually if you arange your code so data follows (which MINIX does)
>since all jumps/calls/rets (except the long vesion) are CS:OFFSET
>you may jump into your data, but not outside of your process space.

Of course, if your data contains the opcode for RETF ...
-----
	Don Kneller
UUCP:	...ucbvax!ucsfcgl!kneller
ARPA:	kneller@cgl.ucsf.edu
BITNET:	kneller@ucsfcgl.BITNET