public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank v Waveren <fvw@var.cx>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>,
	Paul Eggert <eggert@CS.UCLA.EDU>
Subject: Re: [PATCH] prevent timespec/timeval to ktime_t overflow
Date: Sun, 3 Sep 2006 05:13:03 +0200	[thread overview]
Message-ID: <20060903031303.GA26881@var.cx> (raw)
In-Reply-To: <1157222679.29250.386.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]

On Sat, Sep 02, 2006 at 08:44:39PM +0200, Thomas Gleixner wrote:
> On Sat, 2006-09-02 at 13:04 +0200, Frank v Waveren wrote:
> > Here's a different patch, which should actually sleep for the
> > specified amount of time up to 2^64 seconds with a loop around the
> > sleeps and a tally of how long is left to sleep. It does mean we wake
> > up once every 300 years on long sleeps, but that shouldn't cause any
> > huge performance problems.
>
> Which non academic problem is solved by this patch ?
Compared to a current linus kernel, it fixes the overflow problem.
Compared to the current mm (good job on finding the sneaky bug in that
one by the way) it doesn't fix anything additional, but still fixes
all of the same things plus the academic problems. And it makes the
GNU coreutils people happy, which is rarely a bad thing.

-- 
Frank v Waveren                                  Key fingerprint: BDD7 D61E
fvw@var.cx                                              5D39 CF05 4BFC F57A
Public key: hkp://wwwkeys.pgp.net/468D62C8              FA00 7D51 468D 62C8

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-09-03  3:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30  8:44 [PATCH] prevent timespec/timeval to ktime_t overflow Thomas Gleixner
2006-08-30 21:44 ` Frank v Waveren
2006-08-30 22:05   ` Thomas Gleixner
2006-08-30 22:08     ` Frank v Waveren
2006-08-30 22:22       ` Thomas Gleixner
2006-08-30 22:26         ` Frank v Waveren
2006-09-01  3:46 ` Andrew Morton
2006-09-01  8:56   ` Thomas Gleixner
2006-09-01  9:04     ` Andrew Morton
2006-09-01  9:30       ` Thomas Gleixner
2006-09-02  3:13         ` Andrew Morton
2006-09-02  3:32           ` Andrew Morton
2006-09-02  8:08           ` Andi Kleen
2006-09-02 18:41           ` Thomas Gleixner
2006-09-02 19:28             ` Thomas Gleixner
2006-09-02 19:43               ` Andrew Morton
2006-09-02 19:32             ` Andrew Morton
2006-09-02 11:04   ` Frank v Waveren
2006-09-02 18:44     ` Thomas Gleixner
2006-09-03  3:13       ` Frank v Waveren [this message]

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=20060903031303.GA26881@var.cx \
    --to=fvw@var.cx \
    --cc=akpm@osdl.org \
    --cc=eggert@CS.UCLA.EDU \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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