diff options
| author | Christian Borntraeger <borntraeger@de.ibm.com> | 2017-04-09 23:09:38 +0300 |
|---|---|---|
| committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2017-04-12 08:40:24 +0300 |
| commit | a8f60d1fadf7b8b54449fcc9d6b15248917478ba (patch) | |
| tree | 6e0b4aa27aeb23303c60bdef88cff8dd80eaccb4 /tools/perf/scripts/python/stackcollapse.py | |
| parent | c08e611b7d0169b513e3b4515ffd51ac7f37f22c (diff) | |
| download | linux-a8f60d1fadf7b8b54449fcc9d6b15248917478ba.tar.xz | |
s390/mm: fix CMMA vs KSM vs others
On heavy paging with KSM I see guest data corruption. Turns out that
KSM will add pages to its tree, where the mapping return true for
pte_unused (or might become as such later). KSM will unmap such pages
and reinstantiate with different attributes (e.g. write protected or
special, e.g. in replace_page or write_protect_page)). This uncovered
a bug in our pagetable handling: We must remove the unused flag as
soon as an entry becomes present again.
Cc: stable@vger.kernel.org
Signed-of-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions