aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorHugh Dickins <[email protected]>2018-07-20 17:53:45 -0700
committerLinus Torvalds <[email protected]>2018-07-21 12:50:46 -0700
commite1f1b1572e8db87a56609fd05bef76f98f0e456a (patch)
tree97c419c35f7bea38037c6ffa77017fa6ddf1232c /tools/perf/scripts/python/export-to-sqlite.py
parent35033ab988c396ad7bce3b6d24060c16a9066db8 (diff)
mm/huge_memory.c: fix data loss when splitting a file pmd
__split_huge_pmd_locked() must check if the cleared huge pmd was dirty, and propagate that to PageDirty: otherwise, data may be lost when a huge tmpfs page is modified then split then reclaimed. How has this taken so long to be noticed? Because there was no problem when the huge page is written by a write system call (shmem_write_end() calls set_page_dirty()), nor when the page is allocated for a write fault (fault_dirty_shared_page() calls set_page_dirty()); but when allocated for a read fault (which MAP_POPULATE simulates), no set_page_dirty(). Link: http://lkml.kernel.org/r/[email protected] Fixes: d21b9e57c74c ("thp: handle file pages in split_huge_pmd()") Signed-off-by: Hugh Dickins <[email protected]> Reported-by: Ashwin Chaugule <[email protected]> Reviewed-by: Yang Shi <[email protected]> Reviewed-by: Kirill A. Shutemov <[email protected]> Cc: "Huang, Ying" <[email protected]> Cc: <[email protected]> [4.8+] Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions