The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Ingo Molnar <mingo@elte.hu>, Peter Zijlstra <peterz@infradead.org>
Cc: 652732@bugs.debian.org, Vincent Lefevre <vincent@vinc17.net>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Underflow in system time reported by getrusage()
Date: Thu, 29 Dec 2011 17:00:16 +0100	[thread overview]
Message-ID: <1325174416.13595.34.camel@deadeye> (raw)
In-Reply-To: <20111220121401.GA11097@ypig.lip.ens-lyon.fr>

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

On Tue, 2011-12-20 at 13:14 +0100, Vincent Lefevre wrote:
> Package: linux-2.6
> Version: 3.1.5-1
> Severity: minor
> 
> I've had the following problem (under zsh-beta):
> 
> ypig:~> time ./a.out 0.999
> ./a.out 0.999  2.87s user 18446744073.71s system -2147483648% cpu 2.902 total
> 
> Of course, I can't reproduce it. I suppose this problem is quite rare
> and occurs under some particular conditions.

The value reported for system time looks close to the maximum possible
64-bit number of microseconds, presumably resulting from an underflow.

Looking at the Debian source package zsh-beta, version
4.3.15-dev-0+20111220-1, it appears to use getrusage() where available,
and doesn't appear to do any calculations that might cause such
underflow.

Ben.

> I've search on Google and could only find:
> 
>   http://ftp.zcu.cz/mirrors/linux/kernel/v2.6/snapshots/old/patch-2.6.25-git4.log
> 
> which mentions a "very huge system time" problem on IA64 due to
> interrupts. This is unrelated, but could give an idea about a
> possible cause...
[...]

-- 
Ben Hutchings
Design a system any fool can use, and only a fool will want to use it.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

           reply	other threads:[~2011-12-29 16:00 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20111220121401.GA11097@ypig.lip.ens-lyon.fr>]

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=1325174416.13595.34.camel@deadeye \
    --to=ben@decadent.org.uk \
    --cc=652732@bugs.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=vincent@vinc17.net \
    /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