Re: [Qemu-devel] [PATCH v2 11/12] linux-user/aarch64: Reset btype for syscalls and signals

2019-02-04 Thread Richard Henderson
On 2/4/19 12:02 PM, Peter Maydell wrote: > On Mon, 28 Jan 2019 at 22:31, Richard Henderson > wrote: >> >> The value of btype for syscalls is CONSTRAINED UNPREDICTABLE, >> so we need to make sure that the value is 0 before clone, >> fork, or syscall return. >> >> The value of btype for signals is d

Re: [Qemu-devel] [PATCH v2 11/12] linux-user/aarch64: Reset btype for syscalls and signals

2019-02-04 Thread Peter Maydell
On Mon, 28 Jan 2019 at 22:31, Richard Henderson wrote: > > The value of btype for syscalls is CONSTRAINED UNPREDICTABLE, > so we need to make sure that the value is 0 before clone, > fork, or syscall return. > > The value of btype for signals is defined, but it does not make > sense for a SIGILL h

[Qemu-devel] [PATCH v2 11/12] linux-user/aarch64: Reset btype for syscalls and signals

2019-01-28 Thread Richard Henderson
The value of btype for syscalls is CONSTRAINED UNPREDICTABLE, so we need to make sure that the value is 0 before clone, fork, or syscall return. The value of btype for signals is defined, but it does not make sense for a SIGILL handler to enter with the btype set as for the indirect branch that ca