linux-kernel - Re: [PATCH] KVM: VMX: Delete ancient pr_warn() about KVM_SET_TSS

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: <169297955779.2871906.7970773718400668561.b4-ty@google.com>
Date:   Fri, 25 Aug 2023 12:02:42 -0700
From:   Sean Christopherson <seanjc@...gle.com>
To:     Sean Christopherson <seanjc@...gle.com>,
        Paolo Bonzini <pbonzini@...hat.com>
Cc:     kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
        Thorsten Glaser <t.glaser@...ent.de>
Subject: Re: [PATCH] KVM: VMX: Delete ancient pr_warn() about KVM_SET_TSS_ADDR
 not being set

On Tue, 15 Aug 2023 10:42:15 -0700, Sean Christopherson wrote:
> Delete KVM's printk about KVM_SET_TSS_ADDR not being called.  When the
> printk was added by commit 776e58ea3d37 ("KVM: unbreak userspace that does
> not sets tss address"), KVM also stuffed a "hopefully safe" value, i.e.
> the message wasn't purely informational.  For reasons unknown, ostensibly
> to try and help people running outdated qemu-kvm versions, the message got
> left behind when KVM's stuffing was removed by commit 4918c6ca6838
> ("KVM: VMX: Require KVM_SET_TSS_ADDR being called prior to running a VCPU").
> 
> [...]

Applied to kvm-x86 vmx, thanks!

[1/1] KVM: VMX: Delete ancient pr_warn() about KVM_SET_TSS_ADDR not being set
      https://github.com/kvm-x86/linux/commit/9ca0c1a1265c

--
https://github.com/kvm-x86/linux/tree/next
https://github.com/kvm-x86/linux/tree/fixes