Re: Kernel prctl feature for syscall interception and emulation

2020-11-19 Thread Paul Gofman
On 11/19/20 23:54, Paul Gofman wrote: > On 11/19/20 20:57, David Laight wrote: The Windows code is not completely loaded at initialization time. It also has dynamic libraries loaded later. yes, wine knows the memory regions, but there is no guarantee there is a small number of segm

Re: Kernel prctl feature for syscall interception and emulation

2020-11-19 Thread Paul Gofman
On 11/19/20 20:57, David Laight wrote: >>> The Windows code is not completely loaded at initialization time. It >>> also has dynamic libraries loaded later. yes, wine knows the memory >>> regions, but there is no guarantee there is a small number of segments >>> or that the full picture is known

RE: Kernel prctl feature for syscall interception and emulation

2020-11-19 Thread David Laight
> > The Windows code is not completely loaded at initialization time. It > > also has dynamic libraries loaded later. yes, wine knows the memory > > regions, but there is no guarantee there is a small number of segments > > or that the full picture is known at any given moment. > > Yes, I didn't

Re: Kernel prctl feature for syscall interception and emulation

2020-11-19 Thread Rich Felker
On Thu, Nov 19, 2020 at 12:32:54PM -0500, Gabriel Krisman Bertazi wrote: > Rich Felker writes: > > > On Thu, Nov 19, 2020 at 11:15:46AM -0500, Gabriel Krisman Bertazi wrote: > >> Rich Felker writes: > >> > >> > On Wed, Nov 18, 2020 at 01:57:26PM -0500, Gabriel Krisman Bertazi via > >> > Libc-a

Re: Kernel prctl feature for syscall interception and emulation

2020-11-19 Thread Gabriel Krisman Bertazi
Rich Felker writes: > On Thu, Nov 19, 2020 at 11:15:46AM -0500, Gabriel Krisman Bertazi wrote: >> Rich Felker writes: >> >> > On Wed, Nov 18, 2020 at 01:57:26PM -0500, Gabriel Krisman Bertazi via >> > Libc-alpha wrote: >> >> [...] >> >> > >> > SIGSYS (or signal handling in general) is not th

Re: Kernel prctl feature for syscall interception and emulation

2020-11-19 Thread Rich Felker
On Thu, Nov 19, 2020 at 11:15:46AM -0500, Gabriel Krisman Bertazi wrote: > Rich Felker writes: > > > On Wed, Nov 18, 2020 at 01:57:26PM -0500, Gabriel Krisman Bertazi via > > Libc-alpha wrote: > > [...] > > > > > SIGSYS (or signal handling in general) is not the right way to do > > this. It ha

Re: Kernel prctl feature for syscall interception and emulation

2020-11-19 Thread Gabriel Krisman Bertazi
Rich Felker writes: > On Wed, Nov 18, 2020 at 01:57:26PM -0500, Gabriel Krisman Bertazi via > Libc-alpha wrote: [...] > > SIGSYS (or signal handling in general) is not the right way to do > this. It has all the same problems that came up in seccomp filtering > with SIGSYS, and which were solve

Re: Kernel prctl feature for syscall interception and emulation

2020-11-19 Thread Rich Felker
On Wed, Nov 18, 2020 at 01:57:26PM -0500, Gabriel Krisman Bertazi via Libc-alpha wrote: > Hi, > > I'm proposing a kernel patch for a feature I'm calling Syscall User > Dispatch (SUD). It is a mechanism to efficiently redirect system calls > of only part of a binary back to userspace to be emulat

Kernel prctl feature for syscall interception and emulation

2020-11-18 Thread Gabriel Krisman Bertazi
Hi, I'm proposing a kernel patch for a feature I'm calling Syscall User Dispatch (SUD). It is a mechanism to efficiently redirect system calls of only part of a binary back to userspace to be emulated by a compatibility layer. The patchset is close to being accepted, but Florian suggested the fe