summaryrefslogtreecommitdiffstats
path: root/arch/tile/Kconfig
diff options
context:
space:
mode:
authorChris Metcalf <cmetcalf@tilera.com>2010-12-14 21:57:49 +0100
committerChris Metcalf <cmetcalf@tilera.com>2010-12-17 22:56:50 +0100
commitbc4cf2bb271b2d557fc510426755da786fc985be (patch)
tree25fa4e868d810603da82d1a7c800cf1b0eb0d100 /arch/tile/Kconfig
parentMerge branch 'for-2.6.37' of git://linux-nfs.org/~bfields/linux (diff)
downloadlinux-bc4cf2bb271b2d557fc510426755da786fc985be.tar.xz
linux-bc4cf2bb271b2d557fc510426755da786fc985be.zip
arch/tile: handle CLONE_SETTLS in copy_thread(), not user space
Previously we were just setting up the "tp" register in the new task as started by clone() in libc. However, this is not quite right, since in principle a signal might be delivered to the new task before it had its TLS set up. (Of course, this race window still exists for resetting the libc getpid() cached value in the new task, in principle. But in any case, we are now doing this exactly the way all other architectures do it.) This change is important for 2.6.37 since the tile glibc we will be submitting upstream will not set TLS in user space any more, so it will only work on a kernel that has this fix. It should also be taken for 2.6.36.x in the stable tree if possible. Signed-off-by: Chris Metcalf <cmetcalf@tilera.com> Cc: stable <stable@kernel.org>
Diffstat (limited to 'arch/tile/Kconfig')
0 files changed, 0 insertions, 0 deletions