linux-kernel - Re: [GIT PULL] Second batch of KVM changes for Linux 5.18

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: <CAHk-=wgSqvsP08ox-KwAU4TztVsjx07cMQni-rFEzxZQw6+iiA@mail.gmail.com>
Date:   Fri, 1 Apr 2022 13:40:00 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Paolo Bonzini <pbonzini@...hat.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        KVM list <kvm@...r.kernel.org>
Subject: Re: [GIT PULL] Second batch of KVM changes for Linux 5.18

On Fri, Apr 1, 2022 at 8:33 AM Paolo Bonzini <pbonzini@...hat.com> wrote:
>
> The larger change here is support for in-kernel delivery of Xen events
> and timers, but there are also several other smaller features and fixes,
> consisting of 1-2 patches each.

No.

I've had enough with the big random kvm pull requests.

NONE of this has been in linux-next before the merge window. In fact,
None of it was there even the first week of the merge window.

So by all means send me fixes.

But no more of this last-minute development stuff, which clearfly was
not ready to go before the merge window started, and must have been
some wild last-minute merging thing.

kvm needs to make stability as a priority.

              Linus