From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/2] ARM: Fix unparseable signal frame with CONFIG_IWMMXT
Date: Mon, 26 Jun 2017 11:13:04 +0100 [thread overview]
Message-ID: <20170626101304.GG4902@n2100.armlinux.org.uk> (raw)
In-Reply-To: <1498059983-13438-1-git-send-email-Dave.Martin@arm.com>
On Wed, Jun 21, 2017 at 04:46:01PM +0100, Dave Martin wrote:
> 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.
Hmm, I would actually suggest that we poke in a correct size for the
missing iWMMXt record, and an invalid magic number as the "simple"
solution for this - that doesn't make any layout changes to the
data structures, and is probably the safest solution for backporting.
Going forward, I think something along the lines of your proposal is
okay.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2017-06-26 10:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 15:46 [RFC PATCH 0/2] ARM: Fix unparseable signal frame with CONFIG_IWMMXT Dave Martin
2017-06-21 15:46 ` [RFC PATCH 1/2] ARM: iwmmxt: Add missing __user annotations to sigframe accessors Dave Martin
2017-06-21 15:46 ` [RFC PATCH 2/2] ARM: signal: Remove unparseable iwmmxt_sigframe from uc_regspace[] Dave Martin
2017-06-26 10:13 ` Russell King - ARM Linux [this message]
2017-06-26 13:32 ` [RFC PATCH 0/2] ARM: Fix unparseable signal frame with CONFIG_IWMMXT Dave Martin
2017-06-26 14:40 ` Russell King - ARM Linux
2017-06-26 16:36 ` Dave Martin
2017-06-26 18:12 ` Russell King - ARM Linux
2017-06-27 17:15 ` Dave Martin
[not found] ` <AM4PR08MB2659BFF0EAEB020F7571A115D5DF0@AM4PR08MB2659.eurprd08.prod.outlook.com>
2017-07-19 9:28 ` Russell King - ARM Linux
2017-07-19 10:40 ` Dave Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170626101304.GG4902@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).