summaryrefslogtreecommitdiffstats
path: root/fs/sync.c
diff options
context:
space:
mode:
authorWill Deacon <will@kernel.org>2020-08-24 12:28:54 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-08-26 10:27:10 +0200
commit1dee8b843cba4cd7b4d5d454e24ad16d88046bed (patch)
tree46a6014a80339fdcda93454f52f27ff9c439147d /fs/sync.c
parent61e37ca3378f39dffde30c0271cf1f87e8241ce5 (diff)
downloadlinux-stable-1dee8b843cba4cd7b4d5d454e24ad16d88046bed.tar.gz
linux-stable-1dee8b843cba4cd7b4d5d454e24ad16d88046bed.tar.bz2
linux-stable-1dee8b843cba4cd7b4d5d454e24ad16d88046bed.zip
KVM: arm/arm64: Don't reschedule in unmap_stage2_range()
Upstream commits fdfe7cbd5880 ("KVM: Pass MMU notifier range flags to kvm_unmap_hva_range()") and b5331379bc62 ("KVM: arm64: Only reschedule if MMU_NOTIFIER_RANGE_BLOCKABLE is not set") fix a "sleeping from invalid context" BUG caused by unmap_stage2_range() attempting to reschedule when called on the OOM path. Unfortunately, these patches rely on the MMU notifier callback being passed knowledge about whether or not blocking is permitted, which was introduced in 4.19. Rather than backport this considerable amount of infrastructure just for KVM on arm, instead just remove the conditional reschedule. Cc: <stable@vger.kernel.org> # v4.4 only Cc: Marc Zyngier <maz@kernel.org> Cc: Suzuki K Poulose <suzuki.poulose@arm.com> Cc: James Morse <james.morse@arm.com> Signed-off-by: Will Deacon <will@kernel.org> Acked-by: Marc Zyngier <maz@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/sync.c')
0 files changed, 0 insertions, 0 deletions