linux-kernel - Re: [GIT PULL] KVM changes for 4.18 merge window

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: <c982edb3-d2fe-87f9-f1ac-2125901d7013@redhat.com>
Date:   Wed, 13 Jun 2018 16:26:46 +0200
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.18 merge window

On 13/06/2018 15:56, Linus Torvalds wrote:
> On Wed, Jun 13, 2018 at 3:09 AM Paolo Bonzini <pbonzini@...hat.com> wrote:
>>
>> On 13/06/2018 04:18, Linus Torvalds wrote:
>>>
>>> Hmm? And why was this not found before it hit my tree?
>>
>> Because I should do more "make randconfig"s, probably.
> 
> Well, being in linux-next should have found it too. I know linux-next
> had a lot of kvm stuff in it, was this not there?

It was, I suppose that's how Arnd found it.

I also checked my reflog in case I force-pushed something by mistake
(kvm/next doesn't rebase, but you never know) and that didn't happen
either.  I'll fix the "no virt stuff" build in my pre-pull-request
routine.  I already have KVM-but-no-CONFIG_KVM_GUEST build---and the
other way round---I'll remove CONFIG_HYPERV too from the former.

Paolo