summaryrefslogtreecommitdiffstats
path: root/scripts/nsdeps
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2019-11-08 09:43:34 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2019-11-08 09:43:34 -0800
commit9e8ed26e6062e4f585fe831fba362eb567648881 (patch)
tree62f0bcd80f092bacc37722c861702fd0b1c7fe00 /scripts/nsdeps
parent410ef736a77b584e1c54a3784ee56ca63114ce11 (diff)
parent6767df245f4736d0cf0c6fb7cf9cf94b27414245 (diff)
downloadlinux-9e8ed26e6062e4f585fe831fba362eb567648881.tar.bz2
Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Pull arm64 fix from Will Deacon: "Fix pte_same() to avoid getting stuck on write fault. This single arm64 fix is a revert of 747a70e60b72 ("arm64: Fix copy-on-write referencing in HugeTLB"), not because that patch was wrong, but because it was broken by aa57157be69f ("arm64: Ensure VM_WRITE|VM_SHARED ptes are clean by default") which we merged in -rc6. We spotted the issue in Android (AOSP), where one of the JIT threads gets stuck on a write fault during boot because the faulting pte is marked as PTE_DIRTY | PTE_WRITE | PTE_RDONLY and the fault handler decides that there's nothing to do thanks to pte_same() masking out PTE_RDONLY. Thanks to John Stultz for reporting this and testing this so quickly, and to Steve Capper for confirming that the HugeTLB tests continue to pass" * tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux: arm64: Do not mask out PTE_RDONLY in pte_same()
Diffstat (limited to 'scripts/nsdeps')
0 files changed, 0 insertions, 0 deletions