mm/memcontrol.c: make the walk_page_range() limit obvious
authorJames Morse <[email protected]>
Sat, 8 Oct 2016 00:00:12 +0000 (17:00 -0700)
committerLinus Torvalds <[email protected]>
Sat, 8 Oct 2016 01:46:28 +0000 (18:46 -0700)
commit0247f3f4d78a475cd3181dc9fc162fdef773aaaa
tree2e7c179bbed1aa445b8305071dcbf44ce7d299a3
parent6fcb52a56ff60d240f06296b12827e7f20d45f63
mm/memcontrol.c: make the walk_page_range() limit obvious

mem_cgroup_count_precharge() and mem_cgroup_move_charge() both call
walk_page_range() on the range 0 to ~0UL, neither provide a pte_hole
callback, which causes the current implementation to skip non-vma
regions.  This is all fine but follow up changes would like to make
walk_page_range more generic so it is better to be explicit about which
range to traverse so let's use highest_vm_end to explicitly traverse
only user mmaped memory.

[[email protected]: rewrote changelog]
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: James Morse <[email protected]>
Acked-by: Naoya Horiguchi <[email protected]>
Cc: Johannes Weiner <[email protected]>
Cc: Michal Hocko <[email protected]>
Cc: Vladimir Davydov <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
mm/memcontrol.c