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 94BD0C43334 for ; Wed, 29 Jun 2022 15:25:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234012AbiF2PZV (ORCPT ); Wed, 29 Jun 2022 11:25:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36648 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234025AbiF2PZS (ORCPT ); Wed, 29 Jun 2022 11:25:18 -0400 Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9FF9C2C13C for ; Wed, 29 Jun 2022 08:25:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1656516317; x=1688052317; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=Gp6YtP/tV7OzkJtukww4PZaDDGHVNrVauB6vl/EWvMk=; b=SI1bruEJE2UQpa/fkXQSqNY5PTHLsKXvLs//hB55Z+YL/b75UHn0IXAP YhFzXsKsjD7yn3J+wYSqChJgSoW6qxkiBJ3mqoSdrYyJsKTsAy6zPYSzG 7zJxJYbzlvvApdnSsBiRd3yxCN2g+v8/H2sMbyp+LGftKd1j0i+OjBlQt C4OlNApKktVS8Cm1hTYVEHdAoiAxDUF8cDSMUjDSdVGk9gDEltve3+gQ6 lX1ZStEt5f6W3C5Q6AoIHtXNwRuGL/cxrG3L9oooL46/5bcMAa9HV1WLV HyX6fa1pQswNq0l50OunIzxmrvLDFXzCniSn+yRVAuUFV/E0ccCzGYJid w==; X-IronPort-AV: E=McAfee;i="6400,9594,10392"; a="261857934" X-IronPort-AV: E=Sophos;i="5.92,231,1650956400"; d="scan'208";a="261857934" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jun 2022 08:25:17 -0700 X-IronPort-AV: E=Sophos;i="5.92,231,1650956400"; d="scan'208";a="693618747" Received: from djschink-mobl1.amr.corp.intel.com (HELO [10.212.161.74]) ([10.212.161.74]) by fmsmga002-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jun 2022 08:25:16 -0700 Message-ID: <774e5f81-62e3-79e3-4910-39743c4399e0@intel.com> Date: Wed, 29 Jun 2022 08:24:05 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: [REGRESSION] Unable to unlock encrypted disk starting with kernel 5.19-rc1+ Content-Language: en-US To: Alexandre Messier , Thomas Gleixner , Borislav Petkov Cc: linux-kernel@vger.kernel.org, Andrew.Cooper3@citrix.com, mingo@redhat.com, dave.hansen@linux.intel.com, x86@kernel.org, regressions@lists.linux.dev References: <6025678c-e94a-6966-e298-82fad658a889@me.ssier.org> <19f8897b-c445-4e66-49b2-9ceca738a263@me.ssier.org> <874k04e6o4.ffs@tglx> From: Dave Hansen In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/28/22 16:24, Alexandre Messier wrote: > Sorry again for the trouble, this was not a kernel regression, but my error. Been there, done that! I'm just glad we don't have anything to fix. :)