Skip to content

Commit

Permalink
mm/thp/autonuma: use TNF flag instead of vm fault
Browse files Browse the repository at this point in the history
We are using the wrong flag value in task_numa_falt function.  This can
result in us doing wrong numa fault statistics update, because we update
num_pages_migrate and numa_fault_locality etc based on the flag argument
passed.

Fixes: bae473a ("mm: introduce fault_env")
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Aneesh Kumar K.V <[email protected]>
Acked-by: Hillf Danton <[email protected]>
Acked-by: Kirill A. Shutemov <[email protected]>
Cc: Rik van Riel <[email protected]>
Cc: Mel Gorman <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
  • Loading branch information
kvaneesh authored and torvalds committed Feb 25, 2017
1 parent db08f20 commit 9a8b300
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion mm/huge_memory.c
Original file line number Diff line number Diff line change
Expand Up @@ -1506,7 +1506,7 @@ int do_huge_pmd_numa_page(struct vm_fault *vmf, pmd_t pmd)

if (page_nid != -1)
task_numa_fault(last_cpupid, page_nid, HPAGE_PMD_NR,
vmf->flags);
flags);

return 0;
}
Expand Down

0 comments on commit 9a8b300

Please sign in to comment.