linux-kernel - Re: [GIT PULL] KVM: x86 pull requests 6.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 for Android: free password hash cracker in your pocket

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

Message-ID: <aNwsoK82jW97xy9Y@google.com>
Date: Tue, 30 Sep 2025 12:16:48 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] KVM: x86 pull requests 6.18

On Tue, Sep 30, 2025, Paolo Bonzini wrote:
> On Sat, Sep 27, 2025 at 8:09 AM Sean Christopherson <seanjc@...gle.com> wrote:
> >
> > Sorry this is coming in late, it's been a long week.
> >
> > Similar to 6.17, a few anomolies in the form of external and cross-branch
> > dependencies, but thankfully only one conflict that I know of (details in
> > CET pull request).  Oh, and one "big" anomoly: there's a pull request for
> > guest-side x86/kvm changes (but it's small, hence the quotes).
> >
> > I tried my best to document anything unusual in the individual pull requests,
> > so hopefully nothing is too surprising.
> 
> Quite big with CET and the FRED preparations, but no surprises indeed.
> 
> Because of the conflict, I'll delay the bulk of these to a separate
> pull request, probably on Friday.
> 
> I have already included (and tested on top of 6.17) the selftests,
> guest and generic pull request. Everything else in kvm/next. As I
> mentioned in the reply to the individual PR, I ended up cherry-picking
> the module patches.

Roger that.  I updated kvm-x86/next to kvm/next, so we shouldn't get yelled at
for having duplicate commits.

> There were a couple preparatory patches that I guess could have been in misc,

Oh, yeah, that's super obvious in hindsight.

Thanks!