diff options
| author | Rich Felker <dalias@aerifal.cx> | 2011-09-11 12:35:41 -0400 |
|---|---|---|
| committer | Rich Felker <dalias@aerifal.cx> | 2011-09-11 12:35:41 -0400 |
| commit | 8fe5fa56eeade4fc19c5401861c179c2fdfeaf3d (patch) | |
| tree | 2894fdb08fec69e2a1e51e36081f00ac69f2f127 /src/misc | |
| parent | eb351a9e633e5893f0c3bb48808c3ed0280585b5 (diff) | |
| download | musl-8fe5fa56eeade4fc19c5401861c179c2fdfeaf3d.tar.gz musl-8fe5fa56eeade4fc19c5401861c179c2fdfeaf3d.tar.bz2 musl-8fe5fa56eeade4fc19c5401861c179c2fdfeaf3d.tar.xz musl-8fe5fa56eeade4fc19c5401861c179c2fdfeaf3d.zip | |
fix serious bug in pthread_join
on spurious wakeups/returns from __timedwait, pthread_join would
"succeed" and unmap the thread's stack while it was still running. at
best this would lead to SIGSEGV when the thread resumed execution, but
in the worst case, the thread would later resume executing on top of
another new thread's stack mapped at the same address.
spent about 4 hours tracking this bug down, chasing rare
difficult-to-reproduce stack corruption in a stress test program.
still no idea *what* caused the spurious wakeups; i suspect it's a
kernel bug.
Diffstat (limited to 'src/misc')
0 files changed, 0 insertions, 0 deletions