All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: a.zummo@towertech.it, rtc-linux@googlegroups.com,
	linux-kernel@vger.kernel.org
Subject: [rtc-linux] Re: [PATCH] rtc: fix overflow and incorrect calculation in rtc_time64_to_tm
Date: Thu, 3 Dec 2015 21:06:43 -0500	[thread overview]
Message-ID: <5660F533.1070705@oracle.com> (raw)
In-Reply-To: <20151204015554.GB3515@piout.net>

On 12/03/2015 08:55 PM, Alexandre Belloni wrote:
> On 03/12/2015 at 19:12:24 -0500, Sasha Levin wrote :
>> > At some point after humans go extinct and robots cotrol the world, dividing
>> > he time64_t by 86400 to extract the days will overflow a 32bit integer,
>> > leading to incorrect conversion into rtc_time in rtc_time64_to_tm().
>> > 
> And at that time, the robots won't care about 32bit platforms :)

One can only hope... :)

I'll resend.


Thanks,
Sasha

-- 
-- 
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
--- 
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sasha.levin@oracle.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: a.zummo@towertech.it, rtc-linux@googlegroups.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtc: fix overflow and incorrect calculation in rtc_time64_to_tm
Date: Thu, 3 Dec 2015 21:06:43 -0500	[thread overview]
Message-ID: <5660F533.1070705@oracle.com> (raw)
In-Reply-To: <20151204015554.GB3515@piout.net>

On 12/03/2015 08:55 PM, Alexandre Belloni wrote:
> On 03/12/2015 at 19:12:24 -0500, Sasha Levin wrote :
>> > At some point after humans go extinct and robots cotrol the world, dividing
>> > he time64_t by 86400 to extract the days will overflow a 32bit integer,
>> > leading to incorrect conversion into rtc_time in rtc_time64_to_tm().
>> > 
> And at that time, the robots won't care about 32bit platforms :)

One can only hope... :)

I'll resend.


Thanks,
Sasha

  reply	other threads:[~2015-12-04  2:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04  0:12 [rtc-linux] [PATCH] rtc: fix overflow and incorrect calculation in rtc_time64_to_tm Sasha Levin
2015-12-04  0:12 ` Sasha Levin
2015-12-04  0:21 ` [rtc-linux] " kbuild test robot
2015-12-04  0:21   ` kbuild test robot
2015-12-04  1:39 ` [rtc-linux] " kbuild test robot
2015-12-04  1:39   ` kbuild test robot
2015-12-04  1:41 ` [rtc-linux] " kbuild test robot
2015-12-04  1:41   ` kbuild test robot
2015-12-04  1:55 ` [rtc-linux] " Alexandre Belloni
2015-12-04  1:55   ` Alexandre Belloni
2015-12-04  2:06   ` Sasha Levin [this message]
2015-12-04  2:06     ` Sasha Levin

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=5660F533.1070705@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.