> After fixing that in mm/memory.c and mm/filemap.c, the problem seems
> to be properly fixed.
Well, I guess that only leaves the question what
we should do to clean up an OOM situation -- and
if we want a rigorous solution to the problem in
2.2 or if we want to continue deadlocking or killing
random stuff (might be the X server).
But I guess that decision is up to you...
cheers,
Rik -- typing slowly because my kbd is dvorak since sun 19:40...
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/