aboutsummaryrefslogtreecommitdiff
path: root/iconvdata/ibm9030.c
diff options
context:
space:
mode:
authorFlorian Weimer <fweimer@redhat.com>2016-08-02 12:24:50 +0200
committerFlorian Weimer <fweimer@redhat.com>2016-08-04 11:56:22 +0200
commit026671037948fd31009243a2173278dfa0ac9b25 (patch)
tree0bc0fb322230293e6e303c0b38e90bbaf60f226d /iconvdata/ibm9030.c
parente3e0bedf697c8c5858cd7ad1a541a179a20a6320 (diff)
downloadglibc-026671037948fd31009243a2173278dfa0ac9b25.zip
glibc-026671037948fd31009243a2173278dfa0ac9b25.tar.gz
glibc-026671037948fd31009243a2173278dfa0ac9b25.tar.bz2
malloc: Preserve arena free list/thread count invariant [BZ #20370]
It is necessary to preserve the invariant that if an arena is on the free list, it has thread attach count zero. Otherwise, when arena_thread_freeres sees the zero attach count, it will add it, and without the invariant, an arena could get pushed to the list twice, resulting in a cycle. One possible execution trace looks like this: Thread 1 examines free list and observes it as empty. Thread 2 exits and adds its arena to the free list, with attached_threads == 0). Thread 1 selects this arena in reused_arena (not from the free list). Thread 1 increments attached_threads and attaches itself. (The arena remains on the free list.) Thread 1 exits, decrements attached_threads, and adds the arena to the free list. The final step creates a cycle in the usual way (by overwriting the next_free member with the former list head, while there is another list item pointing to the arena structure). tst-malloc-thread-exit exhibits this issue, but it was only visible with a debugger because the incorrect fix in bug 19243 removed the assert from get_free_list. (cherry picked from commit f88aab5d508c13ae4a88124e65773d7d827cd47b)
Diffstat (limited to 'iconvdata/ibm9030.c')
0 files changed, 0 insertions, 0 deletions