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 9DE98C433F5 for ; Fri, 10 Dec 2021 20:11:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344107AbhLJUOv (ORCPT ); Fri, 10 Dec 2021 15:14:51 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53718 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344094AbhLJUOu (ORCPT ); Fri, 10 Dec 2021 15:14:50 -0500 Received: from mail-oi1-x229.google.com (mail-oi1-x229.google.com [IPv6:2607:f8b0:4864:20::229]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5AA08C0617A1 for ; Fri, 10 Dec 2021 12:11:15 -0800 (PST) Received: by mail-oi1-x229.google.com with SMTP id n66so14690058oia.9 for ; Fri, 10 Dec 2021 12:11:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:in-reply-to:message-id:references :mime-version; bh=KOuxIJMKNYTeFBZJypgba4fX+/Q0qIYXKhuuL8rsgx0=; b=jVoZIrcMIhcs34MqmEu4ybtJ5mLwAIvoFS0tyZsRHN4vdJAK/w845YZOVWqDs0cTJ9 zyZqSqx4fdy9fgwK5vH4S+kbFps3bK2u+/N34wWhw5m9GiKK5/JsNEvB5noC2KjZCY3F Xqb+ha3f/RuGPuLBdlIDA3m2rXEfI0QOkqwmn4Iil6ZoshZlDPnAMQhpGISk2HbeumEX Unit1NJWJd3ryBpOJKu5EMDpLo/4/Cjl3i6TCaOHcWmh0GamQpWIXnzjtmbU89W+c+nt 0x68acITGXIkgSXRJkuzZUwV6BTrVCDCYMNJTDKK/9bWdlX+i20vygzsV62Qz14DvYYN Y6ng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version; bh=KOuxIJMKNYTeFBZJypgba4fX+/Q0qIYXKhuuL8rsgx0=; b=Kh8yVj3tjcNHKCQNlTrHtZaxvvcE4wBGMyx3EoBGQeKGwjAnTRU+Oj788QrEF2mXlg kE6eL40YOImU3iobDJ1hUCUagNb1FwOx7VPSTDBkRP1axL4EWeZlOdtrYWPmoQjHQdpd nJ5MOUVu8e/RtmRq83cTN3jeZGe9PwNqDCUtMcUt73CrvfdUx/DdeqnWeDIjaf4amBqj SLM9blANI2kh7WIurxq7eEKQ1MAwfVi2omwO/Xxi68VnU3781Tq7nZsIkoIl/2ems/+M ieg+u8bPYe6BE5FFttx8d996LckO40kYS3+eX+WX53phr+zPRTrltUXygYY+aYk7UXab T1wQ== X-Gm-Message-State: AOAM5310SRUmQmH8Aevj1HwJpSYP6FENXQEPmVY2n3EpGa9rh+mhUtGP ed3Brjoa02V+efeqhhyhxQzL2g== X-Google-Smtp-Source: ABdhPJyii/gnYmnJibARTLGKVefuQ1oitr4zcIVcaAzq7IipapeLfzuP8rfZ9812r9rqo2jWSqft+g== X-Received: by 2002:a54:480b:: with SMTP id j11mr14297800oij.102.1639167074440; Fri, 10 Dec 2021 12:11:14 -0800 (PST) Received: from ripple.attlocal.net (172-10-233-147.lightspeed.sntcca.sbcglobal.net. [172.10.233.147]) by smtp.gmail.com with ESMTPSA id f20sm991153oiw.48.2021.12.10.12.11.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 10 Dec 2021 12:11:14 -0800 (PST) Date: Fri, 10 Dec 2021 12:11:02 -0800 (PST) From: Hugh Dickins X-X-Sender: hugh@ripple.anvils To: Borislav Petkov cc: Mike Rapoport , Juergen Gross , John Dorminy , tip-bot2@linutronix.de, anjaneya.chagam@intel.com, dan.j.williams@intel.com, linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org, stable@vger.kernel.org, x86@kernel.org, Hugh Dickins , "Patrick J. Volkerding" Subject: Re: [tip: x86/urgent] x86/boot: Pull up cmdline preparation and early param parsing In-Reply-To: Message-ID: <297f4912-907-bb45-75df-a030b0d88a8e@google.com> References: <163697618022.414.12673958553611696646.tip-bot2@tip-bot2> <20211209143810.452527-1-jdorminy@redhat.com> <50f25412-d616-1cc6-f07f-a29d80b4bd3b@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 10 Dec 2021, Borislav Petkov wrote: > On Thu, Dec 09, 2021 at 05:37:42PM +0100, Borislav Petkov wrote: > > Whatever we do, it needs to be tested by all folks on Cc who already > > reported regressions, i.e., Anjaneya, Hugh, John and Patrick. > > Ok, Mike is busy so here are some patches for testing: > > https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git/log/?h=rc4-boot > > I'd appreciate it if folks who reported an issue, verify those. > > The first two are reverts which should address the issues with mem= > folks have reported. And the last one should address Anjaneya's issue. > > I guess doing it the way as Mike suggested is cleaner/better. Yes, mem= works fine for me, on both machines, 64-bit and 32-bit, thanks; but I'm not exercising the troublesome EFI case at all. Hugh