diff options
| author |   Matthew Wilcox (Oracle) <willy@infradead.org> | 2020-10-13 16:53:50 -0700 |
|---|---|---|
| committer |   Linus Torvalds <torvalds@linux-foundation.org> | 2020-10-13 18:38:31 -0700 |
| commit | e18c45ffcfa347b13c2f300f290bacff55a4b41e (patch) | |
| tree | 10c75e9baf01f9c4f7deabdd3384ae58730c4038 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | mm: proc: smaps_rollup: do not stall write attempts on mmap_lock (diff) | |
| download | wireguard-linux-e18c45ffcfa347b13c2f300f290bacff55a4b41e.tar.xz wireguard-linux-e18c45ffcfa347b13c2f300f290bacff55a4b41e.zip | |
mm: move PageDoubleMap bit
Patch series "Fix PageDoubleMap".
This is a purely theoretical problem for now as none of the filesystems
which use PG_private_2 (ie PG_fscache) are being converted at this time,
but it's confusing to leave it like this.
This patch (of 2):
PG_private_2 is defined as being PF_ANY (applicable to tail pages as well
as regular & head pages). That means that the first tail page of a
double-map page will appear to have Private2 set. Use the Workingset bit
instead which is defined as PF_HEAD so any attempt to access the
Workingset bit on a tail page will redirect to the head page's Workingset
bit.
Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Zi Yan <ziy@nvidia.com>
Link: https://lkml.kernel.org/r/20200629151933.15671-1-willy@infradead.org
Link: https://lkml.kernel.org/r/20200629151933.15671-2-willy@infradead.org
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions