Bug#904385: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes
- To: 904385@bugs.debian.org
- Subject: Bug#904385: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes
- From: Steve McIntyre <steve@einval.com>
- Date: Wed, 26 Sep 2018 11:41:38 +0100
- Message-id: <[🔎] 20180926104132.kfbpxwmrrx3hz7fi@tack.einval.com>
- Reply-to: Steve McIntyre <steve@einval.com>, 904385@bugs.debian.org
- In-reply-to: <20180725152503.zsdyd7reed5suldp@tack.einval.com>
- References: <153237430026.2128.15229506653308037337.reportbug@arm64.local> <153237430026.2128.15229506653308037337.reportbug@arm64.local> <20180723194033.GB31871@aurel32.net> <20180725152503.zsdyd7reed5suldp@tack.einval.com> <153237430026.2128.15229506653308037337.reportbug@arm64.local>
On Wed, Jul 25, 2018 at 04:25:03PM +0100, Steve McIntyre wrote:
>On Mon, Jul 23, 2018 at 09:40:33PM +0200, Aurelien Jarno wrote:
>>control: affects -1 glibc
>>control: found linux/4.17.6-2
>>
>>On 2018-07-23 21:31, Aurelien Jarno wrote:
>>> Package: src:linux
>>> Version: 4.9.110-1
>>> Severity: normal
>>>
>>> Dear Maintainer,
>>>
>>> The arm64 kernel allows one to run aarch32 processes on an aarch64
>>> processor (if it has support for it), using the standard 32/64-bit
>>> syscall compatibility. However this compat layer does not correctly
>>> validate the arguments of the sigaltstack syscall.
>>>
>>
>>I forgot to say that the problem is reproducible with kernel 4.17.6.
>
>Fix proposed in https://lkml.org/lkml/2018/7/25/409
At Will's suggestion, I've just tested that patchset locally and it
definitely fixes this problem so I've added a Tested-by: for him.
--
Steve McIntyre, Cambridge, UK. steve@einval.com
There's no sensation to compare with this
Suspended animation, A state of bliss
Reply to: