Re: Race condition between memory_object_terminate and RPCs

2010-05-17 Thread olafBuddenhagen
Hi, On Fri, May 14, 2010 at 12:37:25PM +0200, Sergio Lopez wrote: > El Fri, 14 May 2010 06:41:13 +0200 escribió: > > On Tue, May 11, 2010 at 11:48:12AM +0200, Sergio Lopez wrote: > > > I suggest to change m_o_terminate simpleroutine, so it won't > > > transfer memory object control port receive

Re: Race condition between memory_object_terminate and RPCs

2010-05-14 Thread Sergio Lopez
El Fri, 14 May 2010 06:41:13 +0200 escribió: > Hi, > > On Tue, May 11, 2010 at 11:48:12AM +0200, Sergio Lopez wrote: > > [...] > > I suggest to change m_o_terminate simpleroutine, so it won't > > transfer memory object control port receive right to the external > > memory manager, deallocating

Re: Race condition between memory_object_terminate and RPCs

2010-05-13 Thread olafBuddenhagen
Hi, On Tue, May 11, 2010 at 11:48:12AM +0200, Sergio Lopez wrote: [...] > I suggest to change m_o_terminate simpleroutine, so it won't transfer > memory object control port receive right to the external memory > manager, deallocating it in the kernel instead. Unfortunately I do not understand en

Race condition between memory_object_terminate and RPCs

2010-05-11 Thread Sergio Lopez
Hello, When a memory object is being terminated (because a change in its "can_persist" attribute or being cleaned from cache), GNU Mach calls memory_object_terminate. This simpleroutine, sends Mach's receive right on memory object control port to the external memory manager. In Hurd, a translator