xtensa: don't use alternate signal stack on threads
authorBaruch Siach <baruch@tkos.co.il>
Mon, 14 Oct 2013 22:22:43 +0000 (02:22 +0400)
committerBen Hutchings <ben@decadent.org.uk>
Thu, 28 Nov 2013 14:02:04 +0000 (14:02 +0000)
commit06512214e58849e661a67cdc215ca7af26afa58a
treec2c9869ee26a8b8e11893138e22e7b0faaa9f183
parent6c76c2d92d331a029c88355d676cc68982c236d1
xtensa: don't use alternate signal stack on threads

commit cba9a90053e3b7973eff4f1946f33032e98eeed5 upstream.

According to create_thread(3): "The new thread does not inherit the creating
thread's alternate signal stack". Since commit f9a3879a (Fix sigaltstack
corruption among cloned threads), current->sas_ss_size is set to 0 for cloned
processes sharing VM with their parent. Don't use the (nonexistent) alternate
signal stack in this case. This has been broken since commit 29c4dfd9 ([XTENSA]
Remove non-rt signal handling).

Fixes the SA_ONSTACK part of the nptl/tst-cancel20 test from uClibc.

Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Signed-off-by: Chris Zankel <chris@zankel.net>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
arch/xtensa/kernel/signal.c