Wiring up direct socket calls on x86_32 Linux?
From: Andy Lutomirski <luto@amacapital.net>
Date: 2015-06-30 21:15:05
Also in:
lkml
From: Andy Lutomirski <luto@amacapital.net>
Date: 2015-06-30 21:15:05
Also in:
lkml
Hi all- sys_socketcall sucks. If nothing else, it's impossible to filter with seccomp. Should we wire up the real socket calls so that user code can (very slowly) start migrating? I think the list is: - socket - bind - connect - listen - accept4 - getsockname - getpeername - socketpair - send - sendto - sendmsg - recv - recvfrom - recvmsg - shutdown - setsockopt I skipped accept, which is superseded by accept4. sendmmsg and recvmmsg are already wired up. Thoughts? The patch would be trivial. Glibc people: If Linux wired up the syscalls, would glibc use them? --Andy -- Andy Lutomirski AMA Capital Management, LLC