Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1174761

Wiring up direct socket calls on x86_32 Linux?

Show all headers | View raw

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Wiring up direct socket calls on x86_32 Linux? Andy Lutomirski <luto@amacapital.net> - 2015-06-30 23:20 +0200
  Re: Wiring up direct socket calls on x86_32 Linux? Andreas Schwab <schwab@linux-m68k.org> - 2015-06-30 23:30 +0200

csiph-web