diff options
author | David S. Miller <davem@davemloft.net> | 2014-08-04 16:34:01 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2014-08-04 16:34:01 -0700 |
commit | 18f38132528c3e603c66ea464727b29e9bbcb91b (patch) | |
tree | 9600ee863f2b3fc4898ad218a1273cf77fe020d7 /drivers/sbus | |
parent | 31dab719fa50cf56d56d3dc25980fecd336f6ca8 (diff) | |
download | linux-18f38132528c3e603c66ea464727b29e9bbcb91b.tar.bz2 |
sparc64: Do not insert non-valid PTEs into the TSB hash table.
The assumption was that update_mmu_cache() (and the equivalent for PMDs) would
only be called when the PTE being installed will be accessible by the user.
This is not true for code paths originating from remove_migration_pte().
There are dire consequences for placing a non-valid PTE into the TSB. The TLB
miss frramework assumes thatwhen a TSB entry matches we can just load it into
the TLB and return from the TLB miss trap.
So if a non-valid PTE is in there, we will deadlock taking the TLB miss over
and over, never satisfying the miss.
Just exit early from update_mmu_cache() and friends in this situation.
Based upon a report and patch from Christopher Alexander Tobias Schulze.
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/sbus')
0 files changed, 0 insertions, 0 deletions