From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2C59A37DE84 for ; Thu, 9 Apr 2026 12:04:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775736277; cv=none; b=Lxj/C5s+tN3MpnLoO0vsmUIa/eLRYJ+bJuKPC8JfaLVJPGrlVQr8FnzxcIXg7k2IZGRXDX7tWk6+45DmfRSI5Uhw2pbGWTxqXZ0NEMsqXG0bt2Um4QLhspwobcUxFYxv3RUzbWUfSfPA3mXPMRZNyZO6XS4mnNYzuLu7Y2K7MBc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775736277; c=relaxed/simple; bh=gcZxvku11NmaM/oQN+7sEkPtzgRgmTY51fejdl+f4iQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=EKOSmrKLJElVWKqmLF0xqVjVGQySvcnjnUBIMylAOXySiIJMv+pa/17u1Q+gYXv8IOGYtd2lgrR7yn1t/wqyiaRFfB/zyQ9X2rsbDfGSPPDbogA7BnqJOHGNuS14Bm/yVedWBq6YOmuYZ7SkBsT2u4CvZIEsc/PjmjMw/FnR2sg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=QRcRzH4E; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="QRcRzH4E" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9FDE3C4CEF7; Thu, 9 Apr 2026 12:04:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1775736276; bh=gcZxvku11NmaM/oQN+7sEkPtzgRgmTY51fejdl+f4iQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=QRcRzH4ElTvkUK2UDiRPGgoHkPhNfpWtUwSuoa2hKEqYP6G2IulpGTGcXh78j7Unb cv+2aeZFfqDHIYyM9ycPVHx5TbzOLMGI1syCd95GAdtXD+UUu0LIZeDeMSyX+QSOvE lXSrFoSKNinfh4EE8/oSmIMXCg/B08rp04y85z8LUK4Yp4ydsPDBfEZOEWeTf4QRlR kcI+zCjQNk2qkzg58EoMQS4nvuvPkg/X1PWkzbOgH8D1Vm6QV3mOAKj9H923tZP+HX ldNqn/12cjl6IfK6hkex3+Q463rRVVL/tk05/l60JHkk6uUbs1L6UWNmDcEb84JELG PfVMXLtN5Y2+Q== From: Pratyush Yadav To: Breno Leitao Cc: Alexander Graf , Mike Rapoport , Pasha Tatashin , Pratyush Yadav , SeongJae Park , Andrew Morton , kexec@lists.infradead.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, kernel-team@meta.com Subject: Re: [PATCH] kho: call kho_kexec_metadata_init() for both boot paths In-Reply-To: <20260409-kho_fix_merge_issue-v1-1-710c84ceaa85@debian.org> (Breno Leitao's message of "Thu, 09 Apr 2026 03:31:40 -0700") References: <20260409-kho_fix_merge_issue-v1-1-710c84ceaa85@debian.org> Date: Thu, 09 Apr 2026 12:04:32 +0000 Message-ID: <2vxzjyug9w6n.fsf@kernel.org> User-Agent: Gnus/5.13 (Gnus v5.13) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Thu, Apr 09 2026, Breno Leitao wrote: > kho_kexec_metadata_init() was placed after the fdt check, causing it to > run only on the fresh boot path (no incoming FDT) and skipping metadata > initialization on the KHO restore path. > > The original patch[1] was based on commit 5c9e55fecf93658 ("Add linux-next > specific files for 20260312"), which included commit d7176a010afce8 > ("kho: fix deferred init of kho scratch"). That commit has since been > rebased and reworked in linux-next, changing the code flow so that > kho_kexec_metadata_init() is no longer reached on the restore path. > > Fix this by moving the call before the fdt check so it runs regardless > of whether an incoming FDT is present. > > Link: https://lore.kernel.org/all/20260309-kho-v8-5-c3abcf4ac750@debian.org/ [1] > Fixes: 047117e78331a ("kho: kexec-metadata: track previous kernel chain") > Signed-off-by: Breno Leitao Acked-by: Pratyush Yadav Andrew, since the patch "kho: kexec-metadata: track previous kernel chain" is still in mm-unstable, please meld this patch into it if possible. [...] -- Regards, Pratyush Yadav