From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794273758; b=Vs7HMWWCXSp38Yx7QZ3HzbtQhtYncH0FA0tfb8obLP3b9RlUfdpnnc1eLlWOF85Iq57Z Ah8EEuey0UtoNejGDDdm5hiWHzk4s156My6LyO/VQme6fRtoX/jfH1eHT4zRnRi+Yv+o6 aTDi5v+ooMesvC9dg00FeOu9C1bmkE7YCn2iTqK2comGK/vV/wyfSK9XRbHcptCZ/JyBT 0aGkdLFTDAjO92ie+QXWCR6k8lbvU1A0kVNLTgxvCGrchvMuyIbpwibJTRJbRw7VVWInf 5moMzU+TYskZd6iWgHtpstPPfQOZngKrBgGBH8R9TyNS73CKYuFYYDOukCbUIKKY1Ww== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794273758; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: MIME-Version:Content-Type:Content-Transfer-Encoding; bh=+JLc/YYSnL2XHgQM4zvx/j066r/RG+Dsmm9vWdyfvko=; b=q4WTra80aHHaPug5KEmuhK+wxDNbyOklgYW1dXcmEp4EXUrknL4JpSMU7jDXYd60gDtw Ll3o1vU0N6zEYSLNTh+AUFf3bf0sMrY9Dh72/Uc81gO5177I7+nJNYPuDcvSM9UjBZ6fw 812x83bavCB5l5I7kcmoX3IGoxDCAVFJvuDABq1w2Ruoc1ee35DVdltwwL92afOf0weRh aTr/17XDGS1JK+cUs2BgQavfjS44VsSrTrMprSMVda5zmscDCgU9w4ia0y+K4se11ZI1a GRgAUO8yUSQCpim4WY2kAiZwccjxA49U91SIzLfwYoxtoUP9v5/MtYe4igJo9TIYXvA== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=ULuLIarW; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D7705606A31C for ; Tue, 10 Nov 2026 01:22:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=ULuLIarW Received: by smtp.kernel.org (Postfix) with ESMTPSA id E38F11F0089F; Tue, 10 Nov 2026 01:22:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1794273757; bh=+JLc/YYSnL2XHgQM4zvx/j066r/RG+Dsmm9vWdyfvko=; h=From:To:Cc:Subject:Date; b=ULuLIarWztJX8SQBOcv5ww5E21hi3M2wkVWJ2msyfYnnReaQq+G9CutW6CLHucuwZ hEdGPGZ3co0VoQEqrotxBL6gLsrLibt+py30RJXBTHk+xBINA4O0qwSH7Sq5CXpmuN gtuhaCbdsWwldD4qAqi7r/X0nCMnn1PB17AjaE48HBKnP5CcnR13kAeZfR89XTkaW7 Pv5lDFnahgyS/jXfgxOxi2b5X1tQlzJqeshZXLI6rU+ncS/pIAHkRqHyJe9Ufaixbr Riyd4PhvUA3Rt2qyvsBY5VWvBYcjNtir+peg2N1mXf5We9WIVrOx7cmEbxxVV7Wl3v +OYOMlU0CMMsQ== From: Sasha Levin To: namjain@linux.microsoft.com, bp@alien8.de, tglx@kernel.org, vdso@mailbox.org, hargar@linux.microsoft.com, decui@microsoft.com Cc: stable@vger.kernel.org Subject: FAILED: patch "[PATCH] x86/init: Initialize wall clock in get_rtc_noop()" failed to apply to 5.15-stable tree Date: Mon, 9 Nov 2026 20:22:35 -0500 Message-ID: <20261109202235-failed-5.15-7d5af1f256fd@kernel.org> X-Mailer: git-send-email 2.53.0 X-Mailing-List: stable@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The patch below does not apply to the 5.15-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to . To reproduce the conflict and resubmit, you may use the following commands: git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-5.15.y git checkout FETCH_HEAD git cherry-pick -x 7d5af1f256fdecff6a7986bbc9146b69cb355bb5 # git commit -s git send-email --to '' --in-reply-to '20261109202235-failed-5.15-7d5af1f256fd@kernel.org' --subject-prefix 'PATCH 5.15.y' 'HEAD^..' Thanks, Sasha ------------------ original commit in Linus's tree ------------------ >From 7d5af1f256fdecff6a7986bbc9146b69cb355bb5 Mon Sep 17 00:00:00 2001 From: Naman Jain Date: Mon, 31 Aug 2026 08:25:28 +0000 Subject: [PATCH] x86/init: Initialize wall clock in get_rtc_noop() get_rtc_noop() is used when an RTC is unavailable, but leaves its output argument untouched. When CONFIG_INIT_STACK_ALL_ZERO is not enabled, timekeeping_init() may therefore receive a nonzero invalid persistent clock value and warn: "Persistent clock returned invalid value" Initialize the output to zero, the documented representation of an unsupported persistent clock. Fixes: c311ed6183f4 ("x86/init: Allow DT configured systems to disable RTC at boot time") Signed-off-by: Naman Jain Signed-off-by: Borislav Petkov (AMD) Reviewed-by: Thomas Gleixner Reviewed-by: Roman Kisel Reviewed-by: Hardik Garg Reviewed-by: Dexuan Cui Cc: stable@vger.kernel.org Link: https://patch.msgid.link/20260831082528.1623843-1-namjain@linux.microsoft.com --- arch/x86/kernel/x86_init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/kernel/x86_init.c b/arch/x86/kernel/x86_init.c index 252c5827d0634..3b9b41820c84c 100644 --- a/arch/x86/kernel/x86_init.c +++ b/arch/x86/kernel/x86_init.c @@ -37,7 +37,7 @@ static void iommu_shutdown_noop(void) { } bool __init bool_x86_init_noop(void) { return false; } void x86_op_int_noop(int cpu) { } int set_rtc_noop(const struct timespec64 *now) { return -EINVAL; } -void get_rtc_noop(struct timespec64 *now) { } +void get_rtc_noop(struct timespec64 *now) { *now = (struct timespec64){0}; } static __initconst const struct of_device_id of_cmos_match[] = { { .compatible = "motorola,mc146818" }, -- 2.53.0