2.6.11 gave __GFP_ZERO's prep_zero_page a bogus "highmem may have to wait"
assertion. Presumably added under the misconception that clear_highpage
uses nonatomic kmap; but then and now it uses kmap_atomic, so no problem.
Signed-off-by: Hugh Dickins <[EMAIL PROTECTED]>
---
No need for this one in -stable: nobody hit it but me in making other changes.
mm/page_alloc.c | 1 -
1 file changed, 1 deletion(-)
--- 2.6.24-rc3-git/mm/page_alloc.c 2007-11-17 18:45:00.000000000 +0000
+++ linux/mm/page_alloc.c 2007-11-28 17:01:20.000000000 +0000
@@ -305,7 +305,6 @@ static inline void prep_zero_page(struct
{
int i;
- VM_BUG_ON((gfp_flags & (__GFP_WAIT | __GFP_HIGHMEM)) == __GFP_HIGHMEM);
/*
* clear_highpage() will use KM_USER0, so it's a bug to use __GFP_ZERO
* and __GFP_HIGHMEM from hard or soft interrupt context.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
