Re: [PATCH v2] xtensa: don't use alternate signal stack on threads

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Sep 30, 2013 at 1:24 PM, Baruch Siach <baruch@xxxxxxxxxx> wrote:
> 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.
>
> Cc: <stable@xxxxxxxxxxxxxxx>
> Signed-off-by: Baruch Siach <baruch@xxxxxxxxxx>
> ---
> v2: Use sas_ss_flags() as suggested by Max Filippov. Reword commit message.
>
>  arch/xtensa/kernel/signal.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Thanks, applied to my fixes branch.

-- 
Thanks.
-- Max
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]