linux-kernel - Re: [PATCH 02/22] x86/srso: Set CPUID feature bits independently of bug or mitigation status

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: <20230825064209.GCZOhNQf4wP1qWObOG@fat_crate.local>
Date:   Fri, 25 Aug 2023 08:42:09 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Josh Poimboeuf <jpoimboe@...nel.org>
Cc:     Andrew Cooper <andrew.cooper3@...rix.com>, x86@...nel.org,
        linux-kernel@...r.kernel.org,
        Peter Zijlstra <peterz@...radead.org>,
        Babu Moger <babu.moger@....com>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Sean Christopherson <seanjc@...gle.com>, David.Kaplan@....com,
        Nikolay Borisov <nik.borisov@...e.com>,
        gregkh@...uxfoundation.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 02/22] x86/srso: Set CPUID feature bits independently of
 bug or mitigation status

On Thu, Aug 24, 2023 at 03:04:40PM -0700, Josh Poimboeuf wrote:
> Something like this?

Yeah, that's solving the immediate issue but what I mean is, I'd prefer
to have a statement saying:

"This is the use cases Foo and Bar related to live migration which we
want to support because of reasons X and Y."

So that we can know what we're actually supporting. I keep hearing of
cloud vendors doing live migration but nothing about what the kernel
running as a guest needs to support. And whether migration across
generations should be supported. At all. And whether the kernel needs to
even support anything.

And if we don't know the use cases we can't even commit to supporting
them. Or not break them in the future.

And above you can replace "live migration" with any other feature that
is requested. It helps immensely if we know how the kernel is used as
most of us tip maintainers, IMNSVHO, are blissfully unaware of live
migration.

I hope that makes more sense.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette