Bug 741565 - timer_delete does not disarm timer properly
Summary: timer_delete does not disarm timer properly
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.7
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-27 09:56 UTC by Gregor Jasny
Modified: 2011-09-27 11:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-27 11:12:13 UTC
Target Upstream Version:

Attachments (Terms of Use)
testcase (1.10 KB, text/plain)
2011-09-27 09:57 UTC, Gregor Jasny 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Gregor Jasny 2011-09-27 09:56:53 UTC 
Description of problem:
I created a POSIX periodic timer with a 5ms interval. If I delete the timer with timer_delete, I get another callback after the timer_delete returned.

Version-Release number of selected component (if applicable):
glibc-2.5-65

How reproducible:
Execute the attached testcase.

Steps to Reproduce:
1. Run the testcase
  
Actual results:
2. See the error message: "Timer callback for deleted timer"


Expected results:
No timer callbacks after timer_delete returned

This is also reproducible with the Debian eglibc 2.13-21 on amd64.

Thanks,
Gregor
Comment 1 Gregor Jasny 2011-09-27 09:57:29 UTC 
Created attachment 525075 [details]
testcase
Comment 2 Andreas Schwab 2011-09-27 11:12:13 UTC 
The disposition of pending signals for the deleted timer is unspecified.
Note You need to log in before you can comment on or make changes to this bug.