Re: [PATCH] rtc: class: Make the time32 hctosys limit configurable

[sashiko-bot@kernel.org]

> From: Karl Mehltretter <kmehltretter@gmail.com>
> 
> The RTC_HCTOSYS feature faces an impossible dilemma on 32-bit systems:
> 
>  a) systemd requires RTC_HCTOSYS=y with the correct timestamp
>     for its intended operation
> 
>  b) broken RTC hardware can produce random future timestamps
>     beyond 2038 at boot time
> 
>  c) time32 userspace immediately hangs if the time is set to a
>     date beyond 2038 and requires timestamps to be clamped
> 
>  d) time64 userspace is intended to survive the actual 2038
>     date and requires timestamps to not be clamped
> [ ... ]
> Fixes: b3a5ac42ab18 ("rtc: hctosys: Ensure system time doesn't overflow time_t")
> Link: https://lore.kernel.org/all/20220908115337.1604277-1-arnd@kernel.org/
> Assisted-by: LLM
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261020080026.2461578-1-arnd@kernel.org?part=1