Bug 160752 - accounting of SETITIMER_PROF inaccurate
accounting of SETITIMER_PROF inaccurate
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Don Howard
Brian Brock
Depends On:
Blocks: 156320
  Show dependency treegraph
Reported: 2005-06-16 23:53 EDT by Issue Tracker
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version: RHSA-2005-663
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-28 11:23:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
correct behaviour of SIGPROF/itimer. (721 bytes, patch)
2005-06-29 16:58 EDT, Don Howard
no flags Details | Diff
Norm's (correct) original suggestion. (713 bytes, patch)
2005-07-15 03:21 EDT, Don Howard
no flags Details | Diff

  None (edit)
Description Issue Tracker 2005-06-16 23:53:13 EDT
Escalated to Bugzilla from IssueTracker
Comment 12 Don Howard 2005-06-29 16:58:23 EDT
Created attachment 116147 [details]
correct behaviour of SIGPROF/itimer.
Comment 21 Peter Martuccelli 2005-07-13 14:01:50 EDT
Patch has been submitted, pending review, on schedule for release in RHEL3 U6.
Comment 22 Ernie Petrides 2005-07-13 19:38:56 EDT
A fix for this problem has just been committed to the RHEL3 U6
patch pool this evening (in kernel version 2.4.21-32.11.EL).
Comment 23 Tom Kincaid 2005-07-14 09:46:59 EDT
Comment 25 Don Howard 2005-07-15 03:21:06 EDT
Created attachment 116792 [details]
Norm's (correct) original suggestion.
Comment 27 Bryan Mason 2005-07-15 15:07:48 EDT
I just built a test kernel based on 2.4.21-32 and sent it to DreamWorks for testing.
Comment 32 Red Hat Bugzilla 2005-09-28 11:23:30 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.