Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!sdd.hp.com!ucsd!swrinde!emory!mephisto!udel!mmdf
From: root@minixug.hobby.nl (The Master)
Newsgroups: comp.os.minix
Subject: Re: mem_copy problem in MM
Message-ID: <21904@nigel.udel.EDU>
Date: 13 Jun 90 17:58:34 GMT
Sender: mmdf@udel.EDU
Lines: 21

From article <21184@nigel.udel.EDU>, by HBO043%DJUKFA11.BITNET@cunyvm.cuny.edu (Christoph van Wuellen):
> I think you are using 68K-MINIX, since there is a weak point:
No, MUG-MINIX 1.5.10C-PC

> 
> The user program gives an address in his own address space, this must
> be converted to the flat space before using the address.
Yeah, that is why "mem_copy" gets the 'who' parameter ???

> On the ST, this might go since all processes share the same address space
> in reality, but you must not write code like that!
Agreed, but tell this to some calls!
Sometimes, using this kind of code is to be preferred over marshalling
parameters into a single message, like the ioctl() system call does...

> 
> Second: I don't know if MM is allowed to copy something outside its own address
> space (or if it uses the SYSTASK to perform such actions).
Not sure, I think it uses SYSTASK.  I will check on this later...

Fred.