mm/page_alloc.c: fix comment in __get_free_pages()
authorJiankang Chen <[email protected]>
Thu, 1 Feb 2018 00:16:52 +0000 (16:16 -0800)
committerLinus Torvalds <[email protected]>
Thu, 1 Feb 2018 01:18:36 +0000 (17:18 -0800)
__get_free_pages() will return a virtual address, but it is not just a
32-bit address, for example on a 64-bit system.  And this comment really
confuses new readers of mm.

Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Jiankang Chen <[email protected]>
Reported-by: Hanjun Guo <[email protected]>
Cc: Mel Gorman <[email protected]>
Cc: Johannes Weiner <[email protected]>
Cc: Yisheng Xie <[email protected]>
Cc: Kefeng Wang <[email protected]>
Cc: Michal Hocko <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
mm/page_alloc.c

index a73cffe287a552a9924252334e1ab07592105321..b411f97dfb25c2326863df0a124e5a37a651cdc9 100644 (file)
@@ -4278,7 +4278,7 @@ unsigned long __get_free_pages(gfp_t gfp_mask, unsigned int order)
        struct page *page;
 
        /*
-        * __get_free_pages() returns a 32-bit address, which cannot represent
+        * __get_free_pages() returns a virtual address, which cannot represent
         * a highmem page
         */
        VM_BUG_ON((gfp_mask & __GFP_HIGHMEM) != 0);