linux-kernel - Re: [PATCH stable-5.8.y backport 1/2] KVM: Pass MMU notifier range flags to kvm_unmap_hva

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20200824151933.GB435319@kroah.com>
Date:   Mon, 24 Aug 2020 17:19:33 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Will Deacon <will@...nel.org>
Cc:     linux-kernel@...r.kernel.org, maz@...nel.org,
        suzuki.poulose@....com, james.morse@....com, pbonzini@...hat.com,
        kernel-team@...roid.com, stable@...r.kernel.org
Subject: Re: [PATCH stable-5.8.y backport 1/2] KVM: Pass MMU notifier range
 flags to kvm_unmap_hva_range()

On Mon, Aug 24, 2020 at 12:30:47PM +0100, Will Deacon wrote:
> commit fdfe7cbd58806522e799e2a50a15aee7f2cbb7b6 upstream.
> 
> The 'flags' field of 'struct mmu_notifier_range' is used to indicate
> whether invalidate_range_{start,end}() are permitted to block. In the
> case of kvm_mmu_notifier_invalidate_range_start(), this field is not
> forwarded on to the architecture-specific implementation of
> kvm_unmap_hva_range() and therefore the backend cannot sensibly decide
> whether or not to block.
> 
> Add an extra 'flags' parameter to kvm_unmap_hva_range() so that
> architectures are aware as to whether or not they are permitted to block.
> 
> Cc: <stable@...r.kernel.org> # v5.8 only

This matched the 5.8 patch I had already, but I took it just to be safe,
thanks :)

greg k-h