diff options
| author | Andrew Morton <[email protected]> | 2007-09-11 15:24:10 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2007-09-11 17:21:27 -0700 |
| commit | 4150d3f549fe2355625017b2a6ff72aec98bcef0 (patch) | |
| tree | 2d6b7445928c8a295214737a31260d36e9009795 /net/lapb/lapb_timer.c | |
| parent | 298a5df45d497e66064fda22ef0abf13766d3333 (diff) | |
revert "highmem: catch illegal nesting"
Revert
commit 656dad312fb41ed95ef08325e9df9bece3aacbbb
Author: Ingo Molnar <[email protected]>
Date: Sat Feb 10 01:46:36 2007 -0800
[PATCH] highmem: catch illegal nesting
Catch illegally nested kmap_atomic()s even if the page that is mapped by
the 'inner' instance is from lowmem.
This avoids spuriously zapped kmap-atomic ptes and turns hard to find
crashes into clear asserts at the bug site.
Problem is, a get_zeroed_page(GFP_KERNEL) from interrupt context will trigger
this check if non-irq code on this CPU holds a KM_USER0 mapping. But that
get_zeroed_page() will never be altering the kmap slot anyway due to the
GFP_KERNEL.
Cc: Christoph Lameter <[email protected]>
Cc: Ingo Molnar <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions