mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Barry Song <21cnbao@gmail.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: akpm@linux-foundation.org, davem@davemloft.net,
	patrick.ohly@intel.com, uclinux-dist-devel@blackfin.uclinux.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix half-Y2K38 problem in timecompare_update while  calculating offset
Date: Wed, 6 Jan 2010 11:18:37 +0800	[thread overview]
Message-ID: <3c17e3571001051918q7a133a63p64e2b2465dd52a48@mail.gmail.com> (raw)
In-Reply-To: <8bd0f97a1001051128s272f9881q4f1418eba08f1478@mail.gmail.com>

It has been merged into mainline:

timecompare: fix half-Y2K38 problem in timecompare_update while
calculating offset
author	Barry Song <21cnbao@gmail.com>	
	Wed, 16 Dec 2009 00:45:34 +0000 (16:45 -0800)
committer	Linus Torvalds <torvalds@linux-foundation.org>	
	Wed, 16 Dec 2009 15:19:57 +0000 (07:19 -0800)
commit	f065f41f48569122b5bcddbd1ba2354f7cc29fdc
tree	68606305bfb3aba16437017e0596ccae11e6f6db	tree | snapshot
parent	4365a5676fa3aa1d5ae6c90c22a0044f09ba584e	commit | diff
timecompare: fix half-Y2K38 problem in timecompare_update while
calculating offset

ktime will overflow from 03:14:07 UTC on Tuesday, 19 January 2038,
ktime_add() in timecompare_update() will overflow a half earlier.  As a
result, wrong offset will be gotten, then cause some strange problems.

Signed-off-by: Barry Song <21cnbao@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Patrick Ohly <patrick.ohly@intel.com>
Cc: David S. Miller <davem@davemloft.net>
Cc: John Stultz <johnstul@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>


On Wed, Jan 6, 2010 at 3:28 AM, Mike Frysinger <vapier.adi@gmail.com> wrote:
> On Tue, Sep 29, 2009 at 21:44, Mike Frysinger wrote:
>> On Mon, Sep 28, 2009 at 06:16, Barry Song wrote:
>>> ktime will overflow from 03:14:07 UTC on Tuesday, 19 January 2038,
>>> ktime_add() in timecompare_update() will overflow a half earlier.
>>> As a result, wrong offset will be gotten, then cause some strange
>>> problems.
>>
>> Barry: you forgot to include your s-o-b tag ...
>
> you still need to post your s-o-b if we want this to go any further
> -mike
>

  reply	other threads:[~2010-01-06  3:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28 10:16 Barry Song
2009-09-30  2:44 ` Mike Frysinger
2010-01-05 19:28   ` Mike Frysinger
2010-01-06  3:18     ` Barry Song [this message]
2009-09-30  5:35 ` Américo Wang

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=3c17e3571001051918q7a133a63p64e2b2465dd52a48@mail.gmail.com \
    --to=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrick.ohly@intel.com \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=vapier.adi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®