From: ebiederm@xmission.com (Eric W. Biederman)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/2] arm64: fpsimd: Fix bad si_code for undiagnosed SIGFPE
Date: Tue, 23 Jan 2018 13:44:19 -0600 [thread overview]
Message-ID: <87lggo7430.fsf@xmission.com> (raw)
In-Reply-To: <20180123.132916.1025436873838680654.davem@davemloft.net> (David Miller's message of "Tue, 23 Jan 2018 13:29:16 -0500 (EST)")
David Miller <davem@davemloft.net> writes:
> From: ebiederm at xmission.com (Eric W. Biederman)
> Date: Tue, 23 Jan 2018 12:27:16 -0600
>
>> Dave Martin <Dave.Martin@arm.com> writes:
>>
>>> On Mon, Jan 22, 2018 at 03:13:08PM -0600, Eric W. Biederman wrote:
>>> However, the purpose of this as an RFC was to get feedback on whether
>>> adding FPE_UNKNOWN is considered acceptable at all from an API
>>> perspective -- the precise number doesn't matter for that discussion.
>>>
>>> Do you have any view on this?
>>
>> That seems as good a solution as any too me. It is reality and it
>> happens in the code and there are several places of the same form I
>> would use it, just to get rid of the FPE_FIXME.
>
> Eric, feel free to do something similar on Sparc.
Will do.
This sounds like a good solution for this weird corner case, that
appears on multiple architectures.
Eric
next prev parent reply other threads:[~2018-01-23 19:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 12:23 [RFC PATCH 0/2] arm64: Fix invalid si_codes for fault signals Dave Martin
2018-01-22 12:23 ` [RFC PATCH 1/2] arm64: fpsimd: Fix bad si_code for undiagnosed SIGFPE Dave Martin
2018-01-22 21:13 ` Eric W. Biederman
2018-01-23 10:14 ` Dave Martin
2018-01-23 18:27 ` Eric W. Biederman
2018-01-23 18:29 ` David Miller
2018-01-23 19:44 ` Eric W. Biederman [this message]
2018-01-24 9:53 ` Dave Martin
2018-01-24 10:57 ` Dave Martin
2018-01-24 16:47 ` Eric W. Biederman
2018-01-24 17:12 ` Dave Martin
2018-01-24 17:17 ` Eric W. Biederman
2018-01-22 12:23 ` [RFC PATCH 2/2] arm64: signal: Ensure si_code is valid for all fault signals 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=87lggo7430.fsf@xmission.com \
--to=ebiederm@xmission.com \
--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).