Re: [PATCH 04/11] signal/parisc: Document a conflict with SI_USER with SIGFPE

2018-02-26 Thread Eric W. Biederman
Helge Deller writes: > On 23.02.2018 01:15, Eric W. Biederman wrote: >> Helge Deller writes: >> >>> * Eric W. Biederman : Setting si_code to 0 results in a userspace seeing an si_code of 0. This is the same si_code as SI_USER.

Re: [PATCH 04/11] signal/parisc: Document a conflict with SI_USER with SIGFPE

2018-02-26 Thread Eric W. Biederman
Helge Deller writes: > On 23.02.2018 01:15, Eric W. Biederman wrote: >> Helge Deller writes: >> >>> * Eric W. Biederman : Setting si_code to 0 results in a userspace seeing an si_code of 0. This is the same si_code as SI_USER. Posix and common sense requires that SI_USER not be

Re: [PATCH 04/11] signal/parisc: Document a conflict with SI_USER with SIGFPE

2018-02-25 Thread Helge Deller
On 23.02.2018 01:15, Eric W. Biederman wrote: > Helge Deller writes: > >> * Eric W. Biederman : >>> Setting si_code to 0 results in a userspace seeing an si_code of 0. >>> This is the same si_code as SI_USER. Posix and common sense requires >>> that SI_USER

Re: [PATCH 04/11] signal/parisc: Document a conflict with SI_USER with SIGFPE

2018-02-25 Thread Helge Deller
On 23.02.2018 01:15, Eric W. Biederman wrote: > Helge Deller writes: > >> * Eric W. Biederman : >>> Setting si_code to 0 results in a userspace seeing an si_code of 0. >>> This is the same si_code as SI_USER. Posix and common sense requires >>> that SI_USER not be a signal specific si_code. As

Re: [PATCH 04/11] signal/parisc: Document a conflict with SI_USER with SIGFPE

2018-02-22 Thread Eric W. Biederman
Helge Deller writes: > * Eric W. Biederman : >> Setting si_code to 0 results in a userspace seeing an si_code of 0. >> This is the same si_code as SI_USER. Posix and common sense requires >> that SI_USER not be a signal specific si_code. As such this use

Re: [PATCH 04/11] signal/parisc: Document a conflict with SI_USER with SIGFPE

2018-02-22 Thread Eric W. Biederman
Helge Deller writes: > * Eric W. Biederman : >> Setting si_code to 0 results in a userspace seeing an si_code of 0. >> This is the same si_code as SI_USER. Posix and common sense requires >> that SI_USER not be a signal specific si_code. As such this use of 0 >> for the si_code is a pretty

Re: [PATCH 04/11] signal/parisc: Document a conflict with SI_USER with SIGFPE

2018-01-13 Thread Eric W. Biederman
ebied...@xmission.com (Eric W. Biederman) writes: > Helge Deller writes: > >> * Eric W. Biederman : >>> Setting si_code to 0 results in a userspace seeing an si_code of 0. >>> This is the same si_code as SI_USER. Posix and common sense requires >>> that

Re: [PATCH 04/11] signal/parisc: Document a conflict with SI_USER with SIGFPE

2018-01-13 Thread Eric W. Biederman
ebied...@xmission.com (Eric W. Biederman) writes: > Helge Deller writes: > >> * Eric W. Biederman : >>> Setting si_code to 0 results in a userspace seeing an si_code of 0. >>> This is the same si_code as SI_USER. Posix and common sense requires >>> that SI_USER not be a signal specific si_code.

Re: [PATCH 04/11] signal/parisc: Document a conflict with SI_USER with SIGFPE

2018-01-13 Thread Eric W. Biederman
Helge Deller writes: > * Eric W. Biederman : >> Setting si_code to 0 results in a userspace seeing an si_code of 0. >> This is the same si_code as SI_USER. Posix and common sense requires >> that SI_USER not be a signal specific si_code. As such this use

Re: [PATCH 04/11] signal/parisc: Document a conflict with SI_USER with SIGFPE

2018-01-13 Thread Eric W. Biederman
Helge Deller writes: > * Eric W. Biederman : >> Setting si_code to 0 results in a userspace seeing an si_code of 0. >> This is the same si_code as SI_USER. Posix and common sense requires >> that SI_USER not be a signal specific si_code. As such this use of 0 >> for the si_code is a pretty

Re: [PATCH 04/11] signal/parisc: Document a conflict with SI_USER with SIGFPE

2018-01-12 Thread Helge Deller
* Eric W. Biederman : > Setting si_code to 0 results in a userspace seeing an si_code of 0. > This is the same si_code as SI_USER. Posix and common sense requires > that SI_USER not be a signal specific si_code. As such this use of 0 > for the si_code is a pretty horribly

Re: [PATCH 04/11] signal/parisc: Document a conflict with SI_USER with SIGFPE

2018-01-12 Thread Helge Deller
* Eric W. Biederman : > Setting si_code to 0 results in a userspace seeing an si_code of 0. > This is the same si_code as SI_USER. Posix and common sense requires > that SI_USER not be a signal specific si_code. As such this use of 0 > for the si_code is a pretty horribly broken ABI. > >

[PATCH 04/11] signal/parisc: Document a conflict with SI_USER with SIGFPE

2018-01-11 Thread Eric W. Biederman
Setting si_code to 0 results in a userspace seeing an si_code of 0. This is the same si_code as SI_USER. Posix and common sense requires that SI_USER not be a signal specific si_code. As such this use of 0 for the si_code is a pretty horribly broken ABI. Further use of si_code == 0 guaranteed

[PATCH 04/11] signal/parisc: Document a conflict with SI_USER with SIGFPE

2018-01-11 Thread Eric W. Biederman
Setting si_code to 0 results in a userspace seeing an si_code of 0. This is the same si_code as SI_USER. Posix and common sense requires that SI_USER not be a signal specific si_code. As such this use of 0 for the si_code is a pretty horribly broken ABI. Further use of si_code == 0 guaranteed