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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 25C44ECAAD1 for ; Thu, 1 Sep 2022 15:49:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Subject:Cc:To:From:Date:References: In-Reply-To:Message-Id:Mime-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=1McrcQY8v2p4ZZnl2L5TxqmHm1uQqx2MJ6/GDHulB5o=; b=fKBCM+zwULn4m/ 35cUhpZFSBIyisNLVd8JglLHYIzsHfJGj77dIkP0TCi87KVfXWrpjEt3Fc/YN6mSe0TLOIGoFg3/U WHiWvIAEefUvMitKZoebIg3yNcxxig3Hux0/SY08GCXKZZsTkWXmAJa/D62ahsSw84HOqC60HOYp5 R6MhHXc+2iHfHbRIE2Hc5z5MKUTDFnLs3eTJrNyEkgFBYUReN4zno4iPoWdrYa4ehRa7u/giY442w Vt1XyEtrNg97J+Zw12fufbK0AUgQ2IeqQFa0vzywpP1o9TzS9JJulRclLOtYwZcPJgMtHDkOhMQrw nc/8viXvGZPsqQVY8qcA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oTmQd-00D06A-Sw; Thu, 01 Sep 2022 15:48:28 +0000 Received: from wnew1-smtp.messagingengine.com ([64.147.123.26]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oTmQa-00D04U-7y for linux-arm-kernel@lists.infradead.org; Thu, 01 Sep 2022 15:48:25 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.west.internal (Postfix) with ESMTP id 166E72B059BF; Thu, 1 Sep 2022 11:48:23 -0400 (EDT) Received: from imap51 ([10.202.2.101]) by compute3.internal (MEProxy); Thu, 01 Sep 2022 11:48:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arndb.de; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1662047302; x=1662050902; bh=tsFouSTgNC n8v6l3g5PisS2PNQiOZ0CLW9lsweb8bn0=; b=J72WAF6l8NvQpOG5jjL9hDRbia NiuAd2ZoEamIqjIjO4gXM8/h0rJLKtb+zOwhUfWZLtWuw+ye3u6+2nJSiOLLYYLG hJV+jpr2P+r5kP0MyJUejkLkGrbgoWEFfpoFfH3dAMPY0H9GI9aRxEowhFxsg+PM LrSAfRGtHlS/9v2i6JoAPXlhLCfzTKroUhiN9gA7c6BDqWe3fN5NAXZ+EGTj4+5C bl6RG95yXEVXqhdiHX8I7AhrWg942+TkTGCdgoUCPcnjM8c45B4eYOs/lwhxDAyB 24+UVHoOBzP54g0vfBohAZXr5uS5nORc8vkaVikZvO+YJgZ28CcF/MwThv5g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= i56a14606.fm1; t=1662047302; x=1662050902; bh=tsFouSTgNCn8v6l3g5 PisS2PNQiOZ0CLW9lsweb8bn0=; b=kKXXBLvJ/6zjaUS0Mj6JSV2Mp15BSu8jNO 8B1AtFFoBMtwI42+0uAd2ABrbeNxx34ToB/CUZ9a2K9yzUsfaMxDWBXfKOFMjDVw z6aqmyv+IkZ+sYNgY/o209VJAe2ICct8OWRAL+CADA9VgVnNgo4YBIF8/zw10ZGh XcQBHpL9Q5TuN5yMNVPa5Q+bt/waN4vGewGDxbNnqOx4lOAGtx+BtypuCIzbr274 gDwiYoMYPgHQxK479/LBbfjtqVdyGSDdN7f0Fl3eqs83YM5pF6ibtoXizi1WFlRz kJJ3ubapytFOtXPhGwQ2QBtIoPrtw+Ul5rkqu4ktx/SRAPkzo+HQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdekkedgleegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvfevufgtsehttdertderredtnecuhfhrohhmpedftehr nhguuceuvghrghhmrghnnhdfuceorghrnhgusegrrhhnuggsrdguvgeqnecuggftrfgrth htvghrnhepffehueegteeihfegtefhjefgtdeugfegjeelheejueethfefgeeghfektdek teffnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprg hrnhgusegrrhhnuggsrdguvg X-ME-Proxy: Feedback-ID: i56a14606:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 19D87B60083; Thu, 1 Sep 2022 11:48:22 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-841-g7899e99a45-fm-20220811.002-g7899e99a Mime-Version: 1.0 Message-Id: <511f86d8-eadf-40ba-9f0c-022cc4d251fb@www.fastmail.com> In-Reply-To: References: <802ca9c8-4b61-4568-a946-8e6330807eb3@www.fastmail.com> <8eca48d9-bd10-4857-9e43-a5b20a8db625@www.fastmail.com> Date: Thu, 01 Sep 2022 17:48:01 +0200 From: "Arnd Bergmann" To: "Russell King" Cc: "Alexandre Belloni" , linux-arm-kernel@lists.infradead.org, y2038@lists.linaro.org Subject: Re: [Y2038] Re: RTC hctosys disabled for 32-bit systems X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220901_084824_397175_68CDC176 X-CRM114-Status: GOOD ( 21.06 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Sep 1, 2022, at 3:46 PM, Russell King (Oracle) wrote: > On Thu, Sep 01, 2022 at 03:12:57PM +0200, Arnd Bergmann wrote: >> Ah, I forgot that systemd actually needs it. So I guess there is >> currently no way to use systemd on 32-bit machines that are >> meant to survive 2038, regardless of whether systemd and glibc are >> built with a 64-bit time_t or not, right? >> >> Is there perhaps a way to change the logic in a way that >> it does not depend on the current time but instead depends >> on a property of the RTC device itself, so we make systems >> break immediately instead of by surprise in 2038? > > Are you seriously suggesting to cause regressions on systems where > the RTC can send the kernel's timekeeping back to the early 1900s, > rather than printing a big fat warning message in the kernel log? I think the systems that can send the timekeeping back into the early 1900s (or at least after 1970) are fine, the problem is the systems that can randomly send the timekeeping into the post-2038 future. What kind of warning would you suggest to print here? I don't see how warning about broken hardware at every boot would help, since there is no way for users to react to that warning. Similarly, warning about a time_t value past 2038 does not help because at that time one either has a bricked system (if using a systemd with 32-bit time_t) or it is actually 2038 and the system reverts back to 1970. What might work is to have all drivers for broken RTC devices default to a 1902-2037 (or 1970-2037) date range to ensure that only those devices are broken in 2038, but still allow overriding the "start-year" property in DT for machines that don't use the broken systemd. Arnd _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel