Re: [PATCH 1/8] signal/alpha: Document a conflict with SI_USER for SIGTRAP

2017-07-18 Thread Eric W. Biederman
Michael Cree writes: > On Fri, Jul 14, 2017 at 05:59:06AM -0500, Eric W. Biederman wrote: >> in which cases the oddities will happen let alone test them. Plus at >> least for ia64 and alpha those architectures don't appear to be >> receiving updates for new syscalls, and no

Re: [PATCH 1/8] signal/alpha: Document a conflict with SI_USER for SIGTRAP

2017-07-17 Thread Michael Cree
On Fri, Jul 14, 2017 at 05:59:06AM -0500, Eric W. Biederman wrote: > in which cases the oddities will happen let alone test them. Plus at > least for ia64 and alpha those architectures don't appear to be > receiving updates for new syscalls, and no new hardware is being built > so I don't know

Re: [PATCH 1/8] signal/alpha: Document a conflict with SI_USER for SIGTRAP

2017-07-14 Thread Eric W. Biederman
Helge Deller writes: > * Eric W. Biederman : >> Setting si_code to __SI_FAULT 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