linux-kernel - Re: [GIT PULL] KVM changes for 4.16-rc3

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <30581e0c-88f0-8a8e-a620-e5b20027175b@redhat.com>
Date:   Mon, 26 Feb 2018 09:28:27 +0100
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Radim Krčmář <rkrcmar@...hat.com>,
        KVM list <kvm@...r.kernel.org>
Subject: Re: [GIT PULL] KVM changes for 4.16-rc3

On 25/02/2018 01:05, Linus Torvalds wrote:
> On Fri, Feb 23, 2018 at 5:46 PM, Paolo Bonzini <pbonzini@...hat.com> wrote:
>>
>>   git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
> 
> This has 28 fixes that were committed one hour before you sent this email.
> 
> I pulled, but I think I'm going to unpull, just because I want an
> explanation of how that could possibly have had sufficient testing for
> the upcoming rc?

I rebased to correct a "Fixes" tag that pointed to the wrong commit.
This: https://marc.info/?l=kvm&m=151943277910352&w=2 is the mail that
pointed out the right commit, and you can see that those 28 commits have
times that are clustered five minutes after that mail.

The SEV patches indeed have been committed about half an hour before
sending the PULL request, because no one outside AMD has all the
hardware and code to test them.  Half an hour is about the time it takes
me to do the final smoke test before sending a pull request.

Paolo