linux-kernel - Re: [PATCH v6] KVM: x86/tsc: Don't sync user-written TSC against startup values

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: <B2377326-B58D-4D23-9E6E-72C6FB672EB3@infradead.org>
Date:   Sat, 07 Oct 2023 13:51:17 +0100
From:   David Woodhouse <dwmw2@...radead.org>
To:     Like Xu <like.xu.linux@...il.com>,
        Sean Christopherson <seanjc@...gle.com>
CC:     Oliver Upton <oliver.upton@...ux.dev>, kvm@...r.kernel.org,
        linux-kernel@...r.kernel.org, Paolo Bonzini <pbonzini@...hat.com>
Subject: Re: [PATCH v6] KVM: x86/tsc: Don't sync user-written TSC against startup values



On 7 October 2023 08:29:08 BST, Like Xu <like.xu.linux@...il.com> wrote:
>On 25/9/2023 4:31 pm, David Woodhouse wrote:
>> 
>> 
>> On 25 September 2023 09:36:47 CEST, Like Xu <like.xu.linux@...il.com> wrote:
>>> Ping for further comments and confirmation from Sean.
>>> Could we trigger a new version for this issue ? Thanks.
>> 
>> I believe you just have a few tweaks to the comments; I'd resend that as v7.
>
>OK, thanks.
>
>Since I don't seem to have seen V7 yet on the list,
>just let me know if anyone has any new thoughts on this issue.

Ah, the end of my sentence was intended to mean, "(if I were you) I (woul)d resend that as v7."

I didn't mean to suggest that I was actually going to do so myself. So if you didn't post a v7, you won't see it on the list yet :)