Bug#815409: mips qemu-img segfault is due to stack not being executable

2016-06-14 Thread Peter Maydell
On 14 June 2016 at 12:24, Michael Tokarev wrote: > It shouldn't affect qemu-img only, other components should fail > the same way, right? Potentially, yes. It depends whether they have coroutines which happen to execute code that gets compiled into the affected floating point

Bug#815409: mips qemu-img segfault is due to stack not being executable

2016-06-14 Thread Michael Tokarev
Control: forwarded -1 https://lists.nongnu.org/archive/html/qemu-devel/2016-06/msg03272.html 14.06.2016 13:25, Peter Maydell wrote: > I investigated this qemu-img segfault, and it turns out to be > due to a conflict between QEMU not marking its coroutine stacks > as executable and the MIPS

Bug#815409: mips qemu-img segfault is due to stack not being executable

2016-06-14 Thread Peter Maydell
I investigated this qemu-img segfault, and it turns out to be due to a conflict between QEMU not marking its coroutine stacks as executable and the MIPS kernel insisting on an executable stack for floating-point emulation. Full analysis here: