From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 66969 invoked by alias); 21 Jun 2017 15:46:43 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 64436 invoked by uid 89); 21 Jun 2017 15:46:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=BAYES_00,GIT_PATCH_2,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=H*Ad:U*linux, Hx-spam-relays-external:ESMTPA X-Spam-User: qpsmtpd, 2 recipients X-HELO: foss.arm.com From: Dave Martin To: linux-arm-kernel@lists.infradead.org Cc: Russell King , Edmund Grimley-Evans , libc-alpha@sourceware.org, gdb@sourceware.org Subject: [RFC PATCH 0/2] ARM: Fix unparseable signal frame with CONFIG_IWMMXT Date: Wed, 21 Jun 2017 15:46:00 -0000 Message-Id: <1498059983-13438-1-git-send-email-Dave.Martin@arm.com> X-SW-Source: 2017-06/txt/msg01027.txt.bz2 In kernels with CONFIG_IWMMXT=y running on non-iWMMXt hardware, the signal frame can be left partially uninitialised in such a way that userspace cannot parse uc_regspace[] safely. In particular, this means that the VFP registers cannot be located reliably in the signal frame when a multi_v7_defconfig kernel is run on the majority of platforms. I don't know whether any userspace has implemented any sort of workaround for this, but the ABI by itself is insufficient anyway. This series attempts to omit the spurious iWMMXt record when appropriate. Not extensively tested, and the ABI impact is unknown for now. Dave Martin (2): ARM: iwmmxt: Add missing __user annotations to sigframe accessors ARM: signal: Remove unparseable iwmmxt_sigframe from uc_regspace[] arch/arm/include/asm/ucontext.h | 20 ---------------- arch/arm/kernel/signal.c | 52 +++++++++++++++++++++++++++-------------- 2 files changed, 35 insertions(+), 37 deletions(-) -- 2.1.4