On Thu, Nov 19, 2020 at 01:38:27PM +0100, Peter Zijlstra wrote:
> On Tue, Nov 17, 2020 at 10:28:33PM -0500, Gabriel Krisman Bertazi wrote:
> > Gabriel Krisman Bertazi (7):
> > x86: vdso: Expose sigreturn address on vdso to the kernel
> > signal: Expose SYS_USER_DISPATCH si_code type
> >
On Tue, Nov 17, 2020 at 10:28:33PM -0500, Gabriel Krisman Bertazi wrote:
> Gabriel Krisman Bertazi (7):
> x86: vdso: Expose sigreturn address on vdso to the kernel
> signal: Expose SYS_USER_DISPATCH si_code type
> kernel: Implement selective syscall userspace redirection
> entry: Support
* Gabriel Krisman Bertazi:
> The main use case is to intercept Windows system calls of an application
> running over Wine. While Wine is using an unmodified glibc to execute
> its own native Linux syscalls, the Windows libraries might be directly
> issuing syscalls that we need to capture. So
Florian Weimer writes:
> * Gabriel Krisman Bertazi:
>
>> This is the v7 of syscall user dispatch. This version is a bit
>> different from v6 on the following points, after the modifications
>> requested on that submission.
>
> Is this supposed to work with existing (Linux) libcs, or do you
* Gabriel Krisman Bertazi:
> This is the v7 of syscall user dispatch. This version is a bit
> different from v6 on the following points, after the modifications
> requested on that submission.
Is this supposed to work with existing (Linux) libcs, or do you bring
your own low-level run-time
5 matches
Mail list logo