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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a6a6e3936bd130e16ec341628e504adf9d3cb477.camel@redhat.com>
Date:   Mon, 09 Nov 2020 11:43:39 +0200
From:   Maxim Levitsky <mlevitsk@...hat.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Paolo Bonzini <pbonzini@...hat.com>, KVM <kvm@...r.kernel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the kvm-fixes tree

On Mon, 2020-11-09 at 08:14 +1100, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   cc4cb017678a ("KVM: x86: use positive error values for msr emulation that causes #GP")
> 
> Fixes tag
> 
>   Fixes: 291f35fb2c1d1 ("KVM: x86: report negative values from wrmsr emulation to userspace")
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist
> 
> Maybe you meant
> 
> Fixes: 7dffecaf4eab ("KVM: x86: report negative values from wrmsr emulation to userspace")
> 

This is true. Looks like one of my local commits slipped though.
Next time I'll check this more carefully.

Can this be fixed or is it too late?

Best regards,
	Maxim Levitsky

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ