From: ebiederm@xmission.com (Eric W. Biederman)
To: Dave Martin <Dave.Martin@arm.com>
Cc: linux-arch@vger.kernel.org, linux-api@vger.kernel.org,
Will Deacon <will.deacon@arm.com>,
James Morse <james.morse@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/3] arm64: fpsimd: Fix bad si_code for undiagnosed SIGFPE
Date: Thu, 15 Mar 2018 16:13:02 -0500 [thread overview]
Message-ID: <87vadxyrdt.fsf@xmission.com> (raw)
In-Reply-To: <20180309142557.GT32331@e103592.cambridge.arm.com> (Dave Martin's message of "Fri, 9 Mar 2018 14:25:57 +0000")
Dave Martin <Dave.Martin@arm.com> writes:
> On Fri, Mar 09, 2018 at 01:10:18PM +0000, Will Deacon wrote:
>> Hi Eric,
>>
>> On Thu, Mar 08, 2018 at 04:40:12PM -0600, Eric W. Biederman wrote:
>> > Will Deacon <will.deacon@arm.com> writes:
>> > > Happy to take this patch once the dependency on FPE_FLTUNK in core code is
>> > > resolved.
>> >
>> > Would it help for me to take the FPE_FLTUNK patch into my siginfo-next
>> > branch? So that there is a common branch with the code so we don't
>> > need to worry about conflicts. If so I will look at that on Monday.
>>
>> Yes please, that would be helpful actually. I can then pull that into
>> arm64 if you give me a stable branch or tag. Alternatively, I can define
>> FPE_FLTUNK locally and remove it at -rc1.
>
> OK Eric, let me know if you need me to rebase anything for the first 2
> patches.
The first patch is now in my siginfo-next tree and avialable at:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git siginfo-next
HEAD: 266da65e9156d93e1126e185259a4aae68188d0e signal: Add FPE_FLTUNK si_code for undiagnosable fp exceptions
I will not rebase this branch, so please fee free to merge it into other
trees.
Eric
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: Dave Martin <Dave.Martin@arm.com>
Cc: Will Deacon <will.deacon@arm.com>,
linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org,
linux-api@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
James Morse <james.morse@arm.com>
Subject: Re: [PATCH v2 2/3] arm64: fpsimd: Fix bad si_code for undiagnosed SIGFPE
Date: Thu, 15 Mar 2018 16:13:02 -0500 [thread overview]
Message-ID: <87vadxyrdt.fsf@xmission.com> (raw)
Message-ID: <20180315211302._Phik0Qhk3-hh3sZfYYrvDCIssMfGzWssADWN-aPX8k@z> (raw)
In-Reply-To: <20180309142557.GT32331@e103592.cambridge.arm.com> (Dave Martin's message of "Fri, 9 Mar 2018 14:25:57 +0000")
Dave Martin <Dave.Martin@arm.com> writes:
> On Fri, Mar 09, 2018 at 01:10:18PM +0000, Will Deacon wrote:
>> Hi Eric,
>>
>> On Thu, Mar 08, 2018 at 04:40:12PM -0600, Eric W. Biederman wrote:
>> > Will Deacon <will.deacon@arm.com> writes:
>> > > Happy to take this patch once the dependency on FPE_FLTUNK in core code is
>> > > resolved.
>> >
>> > Would it help for me to take the FPE_FLTUNK patch into my siginfo-next
>> > branch? So that there is a common branch with the code so we don't
>> > need to worry about conflicts. If so I will look at that on Monday.
>>
>> Yes please, that would be helpful actually. I can then pull that into
>> arm64 if you give me a stable branch or tag. Alternatively, I can define
>> FPE_FLTUNK locally and remove it at -rc1.
>
> OK Eric, let me know if you need me to rebase anything for the first 2
> patches.
The first patch is now in my siginfo-next tree and avialable at:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git siginfo-next
HEAD: 266da65e9156d93e1126e185259a4aae68188d0e signal: Add FPE_FLTUNK si_code for undiagnosable fp exceptions
I will not rebase this branch, so please fee free to merge it into other
trees.
Eric
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] arm64: fpsimd: Fix bad si_code for undiagnosed SIGFPE
Date: Thu, 15 Mar 2018 16:13:02 -0500 [thread overview]
Message-ID: <87vadxyrdt.fsf@xmission.com> (raw)
In-Reply-To: <20180309142557.GT32331@e103592.cambridge.arm.com> (Dave Martin's message of "Fri, 9 Mar 2018 14:25:57 +0000")
Dave Martin <Dave.Martin@arm.com> writes:
> On Fri, Mar 09, 2018 at 01:10:18PM +0000, Will Deacon wrote:
>> Hi Eric,
>>
>> On Thu, Mar 08, 2018 at 04:40:12PM -0600, Eric W. Biederman wrote:
>> > Will Deacon <will.deacon@arm.com> writes:
>> > > Happy to take this patch once the dependency on FPE_FLTUNK in core code is
>> > > resolved.
>> >
>> > Would it help for me to take the FPE_FLTUNK patch into my siginfo-next
>> > branch? So that there is a common branch with the code so we don't
>> > need to worry about conflicts. If so I will look at that on Monday.
>>
>> Yes please, that would be helpful actually. I can then pull that into
>> arm64 if you give me a stable branch or tag. Alternatively, I can define
>> FPE_FLTUNK locally and remove it at -rc1.
>
> OK Eric, let me know if you need me to rebase anything for the first 2
> patches.
The first patch is now in my siginfo-next tree and avialable at:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git siginfo-next
HEAD: 266da65e9156d93e1126e185259a4aae68188d0e signal: Add FPE_FLTUNK si_code for undiagnosable fp exceptions
I will not rebase this branch, so please fee free to merge it into other
trees.
Eric
next prev parent reply other threads:[~2018-03-15 21:13 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 17:44 [PATCH v2 0/3] arm64: Fix invalid si_codes for fault signals Dave Martin
2018-03-01 17:44 ` Dave Martin
2018-03-01 17:44 ` Dave Martin
2018-03-01 17:44 ` [PATCH v2 1/3] signal: Add FPE_FLTUNK si_code for undiagnosable fp exceptions Dave Martin
2018-03-01 17:44 ` Dave Martin
2018-03-01 17:44 ` Dave Martin
2018-03-08 17:11 ` Will Deacon
2018-03-08 17:11 ` Will Deacon
2018-03-08 22:35 ` Eric W. Biederman
2018-03-08 22:35 ` Eric W. Biederman
2018-03-08 22:35 ` Eric W. Biederman
2018-03-01 17:44 ` [PATCH v2 2/3] arm64: fpsimd: Fix bad si_code for undiagnosed SIGFPE Dave Martin
2018-03-01 17:44 ` Dave Martin
2018-03-01 17:44 ` Dave Martin
2018-03-08 17:11 ` Will Deacon
2018-03-08 17:11 ` Will Deacon
2018-03-08 17:11 ` Will Deacon
2018-03-08 22:40 ` Eric W. Biederman
2018-03-08 22:40 ` Eric W. Biederman
2018-03-08 22:40 ` Eric W. Biederman
2018-03-09 13:10 ` Will Deacon
2018-03-09 13:10 ` Will Deacon
2018-03-09 13:10 ` Will Deacon
2018-03-09 14:25 ` Dave Martin
2018-03-09 14:25 ` Dave Martin
2018-03-09 14:25 ` Dave Martin
2018-03-15 21:13 ` Eric W. Biederman [this message]
2018-03-15 21:13 ` Eric W. Biederman
2018-03-15 21:13 ` Eric W. Biederman
2018-03-20 10:04 ` Will Deacon
2018-03-20 10:04 ` Will Deacon
2018-03-20 10:04 ` Will Deacon
2018-03-08 22:37 ` Eric W. Biederman
2018-03-08 22:37 ` Eric W. Biederman
2018-03-08 22:37 ` Eric W. Biederman
2018-03-01 17:44 ` [PATCH v2 3/3] arm64: signal: Ensure si_code is valid for all fault signals Dave Martin
2018-03-01 17:44 ` Dave Martin
2018-03-01 17:44 ` Dave Martin
2018-03-08 16:37 ` Will Deacon
2018-03-08 16:37 ` Will Deacon
2018-03-08 16:37 ` Will Deacon
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=87vadxyrdt.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=Dave.Martin@arm.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will.deacon@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.