[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
kernel/2182: virtual interval timers always one-shot
- To: gnats@openbsd.org
- Subject: kernel/2182: virtual interval timers always one-shot
- From: cb@mit.edu
- Date: Sat, 17 Nov 2001 18:08:12 -0500 (EST)
- Resent-Date: Sat, 17 Nov 2001 16:20:03 -0700 (MST)
- Resent-From: gnats@cvs.openbsd.org (GNATS Management)
- Resent-Message-Id: <200111172320.fAHNK37a009736@cvs.openbsd.org>
- Resent-Reply-To: gnats@cvs.openbsd.org, cb@mit.edu
- Resent-To: bugs@cvs.openbsd.org
>Number: 2182
>Category: kernel
>Synopsis: virtual interval timers always one-shot
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: bugs
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Sat Nov 17 16:20:01 MST 2001
>Last-Modified:
>Originator:
>Organization:
>Release:
>Environment:
System : OpenBSD 2.9
Architecture: OpenBSD.i386
Machine : i386
>Description:
setitimer() correctly sets and interprets the it_value timer and fires
of a VTALRM. It never reloads the timer, though.
Indeed, kern_clock.c doesn't even *reference* the it_interval field.
This worked before OpenBSD 2.8, but has been broken in 2.8 and 2.9.
>How-To-Repeat:
Use setitimer() to try to performan any virtual time periodic signal
generation. I've only really tried maximum resolution (i.e., using
just 1 microsec).
>Fix:
Unknown. Probably just a little hardclock() hacking.
>Audit-Trail:
>Unformatted: