public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Ivan Grokhotkov <ivan@espressif.com>
To: Udo de Boer <udo.de.boer@ubero.nl>,
	Craig Howland via newlib <newlib@sourceware.org>
Subject: Re: Bug in UTC -> localtime conversion after 2038
Date: Wed, 4 Nov 2020 16:20:56 +0000	[thread overview]
Message-ID: <12D9D3EC-281D-4D29-A4BD-2FDF39188849@espressif.com> (raw)
In-Reply-To: <5d87b235-f246-1bab-f225-484c6fd93b4d@ubero.nl>



> On 4 Nov 2020, at 12:36, Udo de Boer <udo.de.boer@ubero.nl> wrote:
> 
> [External: This email originated outside Espressif]
> 
> Hi,
> 
> UTC time to local timezone conversion did not work for years after 2038.
> Daylight saving in the timezone was not recognized. Tested on 32bit
> xtensa architecture with GCC 8.4 (esp32) and with 64bit time_t enabled.
> 
> The struct tm is filled correct. So year, day etc are all filled with
> the correct values. But the tm.tm_isdst is 0 and no daylight saving is
> applied.
> 
> It was caused by the following calculation in time/tzcalc_limits.c at
> line 68
> 
>       /* store the change-over time in GMT form by adding offset */
>       tz->__tzrule[i].change = days * SECSPERDAY +
>       tz->__tzrule[i].s + tz->__tzrule[i].offset;
> 
> Here tz->__tzrule[i].change is a time_t (64bit). For some reason the
> compiler does the calculation in 32 bit. All variables used in the
> calculation are 32bit.
> 
> I solved this locally by changing the lines to.
> 
>       /* store the change-over time in GMT form by adding offset */
>       tz->__tzrule[i].change = (time_t)days * SECSPERDAY +
>       tz->__tzrule[i].s + tz->__tzrule[i].offset;
> 
> Adding the cast time_t should not cause a problem when time_t is still
> 32bit.
> 
> I don't know if this is correct solution. I also only needed this
> function. So more bugs like this could be hidden away in the time code.
> 
> 
> 
> 
> 
> 
> 


Thank you for reporting and proposing the fix!
Espressif will include this into the next esp32 toolchain release.

For the convenience of the maintainers, I’ve attached the patch below.


Best regards,
Ivan Grokhotkov



From 782c19cd861479cf09a4e2ee27bb7fec1872c626 Mon Sep 17 00:00:00 2001
From: Ivan Grokhotkov <ivan@espressif.com>
Date: Wed, 4 Nov 2020 16:49:51 +0100
Subject: [PATCH] newlib: libc: fix 32-bit integer overflow when calculating TZ
 rules

---
 newlib/libc/time/tzcalc_limits.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/newlib/libc/time/tzcalc_limits.c b/newlib/libc/time/tzcalc_limits.c
index e0ea6549c..00044a5d3 100644
--- a/newlib/libc/time/tzcalc_limits.c
+++ b/newlib/libc/time/tzcalc_limits.c
@@ -66,7 +66,7 @@ __tzcalc_limits (int year)
 	}
 
       /* store the change-over time in GMT form by adding offset */
-      tz->__tzrule[i].change = days * SECSPERDAY +
+      tz->__tzrule[i].change = (time_t) days * SECSPERDAY +
       tz->__tzrule[i].s + tz->__tzrule[i].offset;
     }
 
-- 
2.21.0 (Apple Git-122)






  parent reply	other threads:[~2020-11-04 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 11:36 Udo de Boer
2020-11-04 12:59 ` Richard Damon
2020-11-04 16:20 ` Ivan Grokhotkov [this message]
2020-11-04 18:37   ` Jeff Johnston

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=12D9D3EC-281D-4D29-A4BD-2FDF39188849@espressif.com \
    --to=ivan@espressif.com \
    --cc=newlib@sourceware.org \
    --cc=udo.de.boer@ubero.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).