Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1174761 > unrolled thread
| Started by | Andy Lutomirski <luto@amacapital.net> |
|---|---|
| First post | 2015-06-30 23:20 +0200 |
| Last post | 2015-06-30 23:30 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
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
| From | Andy Lutomirski <luto@amacapital.net> |
|---|---|
| Date | 2015-06-30 23:20 +0200 |
| Subject | Wiring up direct socket calls on x86_32 Linux? |
| Message-ID | <pHb6G-5ld-15@gated-at.bofh.it> |
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/
[toc] | [next] | [standalone]
| From | Andreas Schwab <schwab@linux-m68k.org> |
|---|---|
| Date | 2015-06-30 23:30 +0200 |
| Message-ID | <pHbgn-5xn-15@gated-at.bofh.it> |
| In reply to | #1174761 |
Andy Lutomirski <luto@amacapital.net> writes: > Glibc people: If Linux wired up the syscalls, would glibc use them? Not automatically. It needs to be compatible with the configured minimum kernel version, so runtime probing would needed to be implemented. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- 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/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web