> it ensures mmuflushes in all other processes (sharing that segment) as well. > in fact, the crash you describe just emphasises that point: > the page reference no longer exists, hence the fault. > > the problem (which frankly doesn't bother me) is that fault386 > is being overly cautious in assuming that a page fault that occurs > in system mode but can't map a page successfully is necessarily a kernel bug: > that's not true. it could just note the process instead. > (it doesn't bother me because since unix days i've seen less than a handful > of programs that SHRINK their existing data segments, and i think that's the > only case that can cause the panic you're seeing.)
if this case is really not important, would it make sense to disallow shrinking segments? it might be worth it just to be able to define Eshrinkage. - erik
