diff options
author | Max Filippov <jcmvbkbc@gmail.com> | 2013-05-15 19:02:06 +0400 |
---|---|---|
committer | Chris Zankel <chris@zankel.net> | 2013-06-05 10:14:19 -0700 |
commit | 87962c4db7f594c377d8b0b5a5f563e5f0b5d5d0 (patch) | |
tree | ede110ec898b37350d60af1e66c4b0b7ddbe7ce8 /arch/xtensa/boot | |
parent | 51fc41a90603eaee7b6d03b6027be8f22fcf8ef9 (diff) | |
download | linux-stable-87962c4db7f594c377d8b0b5a5f563e5f0b5d5d0.tar.gz linux-stable-87962c4db7f594c377d8b0b5a5f563e5f0b5d5d0.tar.bz2 linux-stable-87962c4db7f594c377d8b0b5a5f563e5f0b5d5d0.zip |
xtensa: flush TLB entries for pages of non-current mm correctly
Sometimes under high memory pressure one process gets a page of another
process, which manifests itself with an invalid instruction exception.
This happens because flush_tlb_page fails to clear TLB entries when
called with vma that does not belong to current mm, because it does not
set RASID appropriately. When page reclaiming mechanism swaps physical
pages out replacing their PTEs with none or swap PTEs, it calls
flush_tlb_page. Later physical page may be reused elsewhere, but the
stale TLB mapping still refers to it, allowing process that owned the
mapping to see the new state of that physical page.
Put ASID of the mm that owns vma to the RASID to fix that issue.
Also replace otherwise meaningless local_save_flags with local_irq_save.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Signed-off-by: Chris Zankel <chris@zankel.net>
Diffstat (limited to 'arch/xtensa/boot')
0 files changed, 0 insertions, 0 deletions