This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug linuxthreads/12584] New: timer_delete is unsafe
- From: "panruochen at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Tue, 15 Mar 2011 05:59:59 +0000
- Subject: [Bug linuxthreads/12584] New: timer_delete is unsafe
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=12584
Summary: timer_delete is unsafe
Product: glibc
Version: 2.9
Status: NEW
Severity: normal
Priority: P2
Component: linuxthreads
AssignedTo: drow@false.org
ReportedBy: panruochen@gmail.com
Created attachment 5307
--> http://sourceware.org/bugzilla/attachment.cgi?id=5307
Test code for timer_delete issue
Hi All,
I found a bug in timer_delete.
There may be one more unexpected call to the timer signal handler after the
timer has been successfully deleted by timer_delete().
The test code is in the attachment.
I do some tracing into kernel/glibc source, and guess the issue arises in this
way:
The posix_timer_event() function enqueues a signal, timer_delete() does nothing
to dequeue the signal, and the signal will be sent to the user process
asynchronously in schedule().
Best Regards,
PRC
2011/3/15
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.