Commit:     09f345da758fca1222b0971b65b2fddbdf78bb83
Parent:     e84e2e132c9c66d8498e7710d4ea532d1feaaac5
Author:     Hugh Dickins <[EMAIL PROTECTED]>
AuthorDate: Wed Nov 28 18:57:12 2007 +0000
Committer:  Linus Torvalds <[EMAIL PROTECTED]>
CommitDate: Wed Nov 28 11:04:28 2007 -0800

    prep_zero_page: remove bogus BUG_ON
    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]>
    Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
 mm/page_alloc.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 12376ae..4ffed1c 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -305,7 +305,6 @@ static inline void prep_zero_page(struct page *page, int 
order, gfp_t gfp_flags)
        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 git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to