|
From: Julian S. <js...@ac...> - 2005-11-02 15:32:58
|
> > Much the same applies to as_shm as well, which is trying to attach a > > shared memory segment at a high address and expecting it to fail. > > Removing both sounds fine to me. Me too. mremap2 is another problem case. I wrote that to test the mremap handling really carefully, but it does assume that kernel and V make the same layout choices when doing mremap. So it's not robust. Problem is I can't think of a way make it robust without weakening the testing it does. J |