From: Dave Martin <Dave.Martin@arm.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Edmund Grimley-Evans <Edmund.Grimley-Evans@arm.com>,
"gdb@sourceware.org" <gdb@sourceware.org>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH 0/2] ARM: Fix unparseable signal frame with CONFIG_IWMMXT
Date: Wed, 19 Jul 2017 10:40:00 -0000 [thread overview]
Message-ID: <20170719104006.GF3966@e103592.cambridge.arm.com> (raw)
In-Reply-To: <20170719092827.GA28445@n2100.armlinux.org.uk>
On Wed, Jul 19, 2017 at 10:28:27AM +0100, Russell King - ARM Linux wrote:
> On Mon, Jun 26, 2017 at 03:14:13PM +0000, Edmund Grimley-Evans wrote:
> > As a user (I recently implemented a work-around for this problem in DynamoRIO: https://github.com/DynamoRIO/dynamorio/commit/0b75c635033d01ab04f955f5affe14a3ced9ab56) I'm happy with any of the proposed solutions, provided that in the "invalid magic number" case user space is not required to regenerate the bogus block with the same invalid magic number when invoking sigreturn.
>
> I have to ask why a bug report was never sent to kernel people on this.
> If no one tells people that software is buggy, that software stands
> little chance of being fixed!
Partly because I fielded it before it got raised on the list.
However, it would have been good to have more discussion on the list and
to get the DynamoRIO guys commenting on there -- since they are the ones
actually trying to use this feature.
I'll try to encourage that more in the future...
Cheers
---Dave
prev parent reply other threads:[~2017-07-19 10:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 15:46 Dave Martin
2017-06-21 15:47 ` [RFC PATCH 2/2] ARM: signal: Remove unparseable iwmmxt_sigframe from uc_regspace[] Dave Martin
2017-06-21 15:47 ` [RFC PATCH 1/2] ARM: iwmmxt: Add missing __user annotations to sigframe accessors Dave Martin
2017-06-26 10:13 ` [RFC PATCH 0/2] ARM: Fix unparseable signal frame with CONFIG_IWMMXT Russell King - ARM Linux
2017-06-26 13:33 ` 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 [this message]
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=20170719104006.GF3966@e103592.cambridge.arm.com \
--to=dave.martin@arm.com \
--cc=Edmund.Grimley-Evans@arm.com \
--cc=gdb@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
/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