In the following patches, new zone, ZONE_CMA, will be introduced and
it would be overlapped with other zones. Currently, many places
iterating pfn range doesn't consider possibility of zone overlap and
this would cause a problem such as printing wrong statistics information.
To prevent this situation, this patch add some code to consider zone
overlapping before adding ZONE_CMA.

pagetypeinfo_showblockcount_print() prints zone's statistics so should
consider zone overlap.

Signed-off-by: Joonsoo Kim <iamjoonsoo....@lge.com>
---
 mm/vmstat.c |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/mm/vmstat.c b/mm/vmstat.c
index 1b12d39..7a4ac8e 100644
--- a/mm/vmstat.c
+++ b/mm/vmstat.c
@@ -984,6 +984,8 @@ static void pagetypeinfo_showblockcount_print(struct 
seq_file *m,
                        continue;
 
                page = pfn_to_page(pfn);
+               if (page_zone(page) != zone)
+                       continue;
 
                /* Watch for unexpected holes punched in the memmap */
                if (!memmap_valid_within(pfn, page, zone))
-- 
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to