From: Joonsoo Kim <iamjoonsoo.kim@xxxxxxx>
Change from v1
o drop patch 1 ("mm/page_alloc: fix same zone check in
__pageblock_pfn_to_page()") per Mel's comment
Hello, all.
This patchset deals with some problematic sites that iterate pfn range.
There is a system that node's pfn are overlapped like as following.
-----pfn-------->
N0 N1 N2 N0 N1 N2
Therefore, we need to care this overlapping when iterating pfn range.
I audit many iterating sites that uses pfn_valid(), pfn_valid_within(),
zone_start_pfn and etc. and others looks safe for me. This is
a preparation step for new CMA implementation, ZONE_CMA [1], because
it would be easily overlapped with other zones. But, zone overlap
check is also needed for general case so I send it separately.
This is based on next-20160330.
Thanks.
[1]: https://lkml.org/lkml/2015/2/12/95
Joonsoo Kim (5):
mm/hugetlb: add same zone check in pfn_range_valid_gigantic()
mm/memory_hotplug: add comment to some functions related to memory
hotplug
mm/vmstat: add zone range overlapping check
mm/page_owner: add zone range overlapping check
power: add zone range overlapping check
mm/hugetlb.c | 9 ++++++---
mm/page_alloc.c | 7 ++++++-
mm/page_isolation.c | 1 +
mm/page_owner.c | 3 +++
mm/vmstat.c | 7 +++++++
5 files changed, 23 insertions(+), 4 deletions(-)
--
1.9.1
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>