diff options
author | David Hildenbrand <[email protected]> | 2024-01-22 18:17:51 +0100 |
---|---|---|
committer | Andrew Morton <[email protected]> | 2024-01-25 23:52:21 -0800 |
commit | e4e3df290f65da6cb27dac1309389c916f27db1a (patch) | |
tree | 0f6edd6893d61afe246d8a8b14458f3e9ade7d36 /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/EventClass.py | |
parent | db44c658f798ad907219f15e033229b8d1aadb93 (diff) |
mm/memory: fix folio_set_dirty() vs. folio_mark_dirty() in zap_pte_range()
The correct folio replacement for "set_page_dirty()" is
"folio_mark_dirty()", not "folio_set_dirty()". Using the latter won't
properly inform the FS using the dirty_folio() callback.
This has been found by code inspection, but likely this can result in some
real trouble when zapping dirty PTEs that point at clean pagecache folios.
Yuezhang Mo said: "Without this fix, testing the latest exfat with
xfstests, test cases generic/029 and generic/030 will fail."
Link: https://lkml.kernel.org/r/[email protected]
Fixes: c46265030b0f ("mm/memory: page_remove_rmap() -> folio_remove_rmap_pte()")
Signed-off-by: David Hildenbrand <[email protected]>
Reported-by: Ryan Roberts <[email protected]>
Closes: https://lkml.kernel.org/r/[email protected]
Reviewed-by: Ryan Roberts <[email protected]>
Cc: Matthew Wilcox (Oracle) <[email protected]>
Reviewed-by: Yuezhang Mo <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/EventClass.py')
0 files changed, 0 insertions, 0 deletions