Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!+ From: Robert.Sansom@CS.CMU.EDU Newsgroups: comp.os.mach Subject: Re: MIG+netmsgserver bug? Message-ID: Date: 13 Nov 90 00:40:44 GMT References: <9011110250.AA29362@cs.columbia.edu> Organization: Carnegie Mellon, Pittsburgh, PA Lines: 14 In-Reply-To: <9011110250.AA29362@cs.columbia.edu> As Rich Draves said, this is not the fault of the netmsgserver. The root of the problem is that the msg_type_deallocate field should not be part of the type description for something in the message. It is really just an indication to the LOCAL kernel that the data should be deallocated from the sending task's address space. Since the netmsgserver does not want this to happen, it sets the deallocate bit to FALSE (as the comment says---the comment should have said "Always set deallocate bit to FALSE so that we don't accidentally deallocate parts of our address space." or something to that effect). Robert Sansom, School of Computer Science Carnegie Mellon University, Pittsburgh, PA 15213 INTERNET: sansom@cs.cmu.edu CSNET: sansom%cs.cmu.edu@relay.cs.net BITNET: sansom%cs.cmu.edu@cmuccvma UUCP: ...!seismo!cs.cmu.edu!sansom