This service will be undergoing maintenance at 20:00 UTC, 2017-04-03. It is expected to last about 30 minutes
Bug 132319 - task_struct leak in posix-timers
task_struct leak in posix-timers
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Roland McGrath
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2004-09-10 17:05 EDT by Roland McGrath
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-12 05:29:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
test program to show timer_create leaking task_structs (809 bytes, text/plain)
2004-09-10 17:06 EDT, Roland McGrath
no flags Details
fix for task_struct leak in timer_create (1.14 KB, patch)
2004-09-10 17:09 EDT, Roland McGrath
no flags Details | Diff

  None (edit)
Description Roland McGrath 2004-09-10 17:05:14 EDT
Description of problem:

timer_create with other than SIGEV_THREAD_ID leaks a task_struct.

Version-Release number of selected component (if applicable):
2.6.9-rc1, let's say

How reproducible:

Steps to Reproduce:
1. use timer_create over and over in new processes,
   e.g. try attached test program 
2. check slabtop
3. watch task_struct count grow out of control
Actual results:


Expected results:

no leak 

Additional info:

fix on the way
Comment 1 Roland McGrath 2004-09-10 17:06:01 EDT
Created attachment 103703 [details]
test program to show timer_create leaking task_structs

gcc -o timerleak -g timerleak.c -lrt -Wall
Comment 2 Roland McGrath 2004-09-10 17:09:57 EDT
Created attachment 103704 [details]
fix for task_struct leak in timer_create

I've submitted this fix upstream.
Comment 3 Roland McGrath 2004-09-12 05:29:41 EDT
Fix went into Linus's tree.

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