I think the correct way to fix this is to directly call
check_pgt_cache() after unloading the page tables.
No, the correct fix is to see if the count is > the high water mark,
and directly free the page if so, not to expensively call the
check_pgt_cache() function.
It is a bug, but I wonder when it would actually happen in real
operation. I can run "swap-stress" which eats %99.5 of all memory and
swap, and has a stupid spin loop to guarentee the idle thread never
runs, and get fork failures, what have I proven?
Later,
David S. Miller
davem@dm.cobaltmicro.com
-
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.altern.org/andrebalsa/doc/lkml-faq.html