summaryrefslogtreecommitdiffstats
path: root/meta/recipes-connectivity
diff options
context:
space:
mode:
authorYuanjie Huang <Yuanjie.Huang@windriver.com>2017-03-28 19:38:34 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-05-18 13:07:34 +0100
commitb37b775e775ce162c268ec95d62fee8dd5caf81c (patch)
tree45a61f37ef2f426f256e5c8b73521bb3f988ce8d /meta/recipes-connectivity
parentc90540df8b72bf9fe342bb39b3029ede39be2aeb (diff)
downloadpoky-b37b775e775ce162c268ec95d62fee8dd5caf81c.tar.gz
glibc: Fix use after free in pthread_create()
[BZ 20116] -- https://sourceware.org/bugzilla/show_bug.cgi?id=20116 The commit documents the ownership rules around 'struct pthread' and when a thread can read or write to the descriptor. With those ownership rules in place it becomes obvious that pd->stopped_start should not be touched in several of the paths during thread startup, particularly so for detached threads. In the case of detached threads, between the time the thread is created by the OS kernel and the creating thread checks pd->stopped_start, the detached thread might have already exited and the memory for pd unmapped. As a regression test we add a simple test which exercises this exact case by quickly creating detached threads with large enough stacks to ensure the thread stack cache is bypassed and the stacks are unmapped. Before the fix the testcase segfaults, after the fix it works correctly and completes without issue. For a detailed discussion see: https://www.sourceware.org/ml/libc-alpha/2017-01/msg00505.html (cherry-picked from commit f8bf15febcaf137bbec5a61101e88cd5a9d56ca8) (From OE-Core rev: eaa844b6ce75d68f952de67ea5145a54a1968171) Signed-off-by: Yuanjie Huang <yuanjie.huang@windriver.com> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-connectivity')
0 files changed, 0 insertions, 0 deletions