From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id AF0AEEB64DD for ; Sat, 12 Aug 2023 02:57:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236005AbjHLC51 (ORCPT ); Fri, 11 Aug 2023 22:57:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40974 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235619AbjHLC5Z (ORCPT ); Fri, 11 Aug 2023 22:57:25 -0400 Received: from mail-pf1-x44a.google.com (mail-pf1-x44a.google.com [IPv6:2607:f8b0:4864:20::44a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 46F523582 for ; Fri, 11 Aug 2023 19:57:24 -0700 (PDT) Received: by mail-pf1-x44a.google.com with SMTP id d2e1a72fcca58-68714deeba7so3370518b3a.0 for ; Fri, 11 Aug 2023 19:57:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1691809044; x=1692413844; h=content-transfer-encoding:cc:to:from:subject:message-id:references :mime-version:in-reply-to:date:from:to:cc:subject:date:message-id :reply-to; bh=tS5bjxGvXHgpjsR89BBAVK24EK+MfHyO8qai22TwsEE=; b=0xRjApE/U2RYFS+YWsLHyC/7iP6MlrHOrokf6+FnoBtk43mlqfsrwUv8M/FWPvEMxR n/IlPK4ZSgwFLSbugSEe11CEcWK596MYNaTc12vJSoAXiB1Q1S7E8n37GfCZUNiVvLzI mRF9H2wv+hFDorBRRf0l7Sw+fQIW7GKXBv+wgFEO59Y6UibZvqkgqZo5NUb1VE42c153 /A+4DJCLf+ZnVVCqjLqNnGQGAo6FN6HMe3AJ52aiNQVCOQjPj7XO79l+tXRnicRvwlOn T6m2ifmiho+Xy1m3EYbG0oKMwPo60tZZE6K5+uLlTIsCqNkCdnZkE3mujYPrz/swJMoL SLng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691809044; x=1692413844; h=content-transfer-encoding:cc:to:from:subject:message-id:references :mime-version:in-reply-to:date:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=tS5bjxGvXHgpjsR89BBAVK24EK+MfHyO8qai22TwsEE=; b=M8tpi5XtbaMBOzsjgzOJKYsRcCI0jx0HQfXS9s4X2apK4glkxEgWdzwnvKq7ropedM sbLtYqUeOWH+sF8lFn616egES3n8ymVuhDDZaw5A/6OgLZO+7WoHGwAGw7xFm+81rYlW l6kOqxLfqmjmOMnIGtTM646EbjX/8OX5BBVCLFDXKDcnxtpnQX088395F5VhjdBeXyOO 8e2esv5gGiGxNrxZ/FxhjVPOSyLrK58+TVzKXZRh8BaRIaubvd2jnMP+uFcGn2eDXDdn coKl59J90dQ1K2v0PCRhzRKdNE7geeDgonBkOt7Ihz+ouz7VQu3btt3F0e+TtjzFE3BE 91+A== X-Gm-Message-State: AOJu0Ywn72lwuvzYj0gqAw7WXZm+tARiOlCU0oxXd4++fjWi2z/gg8TX djp5UICT6AIo3LcYGuNo8WZKMrfGpMc= X-Google-Smtp-Source: AGHT+IFUZBQeQ6IXU+PWByB0C9HZCEmzHADTXcVvXMNbSAzt3QPkvaokh4WVr9x/O5cMStF3DhjL4D6etL0= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a05:6a00:3928:b0:686:df16:f887 with SMTP id fh40-20020a056a00392800b00686df16f887mr1611366pfb.6.1691809043752; Fri, 11 Aug 2023 19:57:23 -0700 (PDT) Date: Fri, 11 Aug 2023 19:57:22 -0700 In-Reply-To: <8edc91f9-ce20-9528-a496-5b6e650bb63f@redhat.com> Mime-Version: 1.0 References: <20230811155255.250835-1-seanjc@google.com> <8edc91f9-ce20-9528-a496-5b6e650bb63f@redhat.com> Message-ID: Subject: Re: [PATCH] x86/retpoline: Don't clobber RFLAGS during srso_safe_ret() From: Sean Christopherson To: "Mika =?utf-8?B?UGVudHRpbMOk?=" Cc: Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, linux-kernel@vger.kernel.org, Srikanth Aithal , kvm@vger.kernel.org, Paolo Bonzini Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Fri, Aug 11, 2023, Mika Penttil=C3=A4 wrote: > > @@ -252,11 +252,10 @@ SYM_START(srso_untrain_ret, SYM_L_GLOBAL, SYM_A_N= ONE) > > .byte 0x48, 0xb8 > > SYM_INNER_LABEL(srso_safe_ret, SYM_L_GLOBAL) > > - add $8, %_ASM_SP > > + lea 8(%_ASM_SP), %_ASM_SP > > ret > > int3 > > int3 > > - int3 > > lfence > > call srso_safe_ret > > int3 > >=20 > > base-commit: 25aa0bebba72b318e71fe205bfd1236550cc9534 >=20 > Don't we have the same kind of problems with __x86_return_skl ? Yep, forcing that path via "retbleed=3Dforce retbleed=3Dstuff spectre_v2=3D= retpoline,generic" yields the same failures. I have no idea how to go about cleanly fixing th= at. The logic effectively requires modifying flags, the only thing I can think = of is to save/restore flags across the thunk, which seems beyond gross. Given that no one has complained about this, I think I'd vote to simply dis= able KVM if call depth tracking is being used.