On 24.05.2018 13:51, Kamil Rytarowski wrote: > On 24.05.2018 12:48, Martin Husemann wrote: >> On Thu, May 24, 2018 at 10:33:11AM +0000, Martin Husemann wrote: >>> so there are even more bugs :-/ >> >> To sum up: both syscall(2) and __syscall(2) are very hard to use and do not >> really provide any value. >> > > I agree that it's not optimal. I made a resarch but perhaps only IRIX > had no usable syscall(2) BSD4-style call. > > I will try to research and propose an alternative for indirect system call. > It looks like there is no better within the C ABI to serialize arbitrary arguments. We want for example 2 integers returned from SYS_pipe. I'm going to switch sanitizers to dlsym(3) trickery (RTLD_NEXT) and see how good it will work.
Attachment:
signature.asc
Description: OpenPGP digital signature