* Wiring up direct socket calls on x86_32 Linux?
@ 2015-06-30 21:14 Andy Lutomirski
2015-06-30 21:29 ` Andreas Schwab
2015-07-01 16:19 ` Tulio Magno Quites Machado Filho
0 siblings, 2 replies; 4+ messages in thread
From: Andy Lutomirski @ 2015-06-30 21:14 UTC (permalink / raw)
To: X86 ML, linux-kernel@vger.kernel.org
Cc: Alexander Larsson, Cosimo Cecchi, Dan Nicholson,
Network Development, libc-alpha
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Wiring up direct socket calls on x86_32 Linux?
2015-06-30 21:14 Wiring up direct socket calls on x86_32 Linux? Andy Lutomirski
@ 2015-06-30 21:29 ` Andreas Schwab
2015-07-01 16:19 ` Tulio Magno Quites Machado Filho
1 sibling, 0 replies; 4+ messages in thread
From: Andreas Schwab @ 2015-06-30 21:29 UTC (permalink / raw)
To: Andy Lutomirski
Cc: X86 ML, linux-kernel@vger.kernel.org, Alexander Larsson,
Cosimo Cecchi, Dan Nicholson, Network Development, libc-alpha
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."
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Wiring up direct socket calls on x86_32 Linux?
2015-06-30 21:14 Wiring up direct socket calls on x86_32 Linux? Andy Lutomirski
@ 2015-07-01 16:19 ` Tulio Magno Quites Machado Filho
2015-07-01 16:19 ` Tulio Magno Quites Machado Filho
1 sibling, 0 replies; 4+ messages in thread
From: Tulio Magno Quites Machado Filho @ 2015-07-01 16:19 UTC (permalink / raw)
To: Andy Lutomirski
Cc: X86 ML, linux-kernel@vger.kernel.org, Alexander Larsson,
Cosimo Cecchi, Dan Nicholson, Network Development, libc-alpha,
Rajalakshmi Srinivasaraghavan
Andy Lutomirski <luto@amacapital.net> writes:
> 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 guess you might want to follow the patch Raji sent today [1].
Her patch doesn't have all the syscalls you mentioned here, but has others too.
She will work to get a generic implementation for these functions.
[1] http://patchwork.sourceware.org/patch/7438/
--
Tulio Magno
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Wiring up direct socket calls on x86_32 Linux?
@ 2015-07-01 16:19 ` Tulio Magno Quites Machado Filho
0 siblings, 0 replies; 4+ messages in thread
From: Tulio Magno Quites Machado Filho @ 2015-07-01 16:19 UTC (permalink / raw)
To: Andy Lutomirski
Cc: X86 ML, linux-kernel@vger.kernel.org, Alexander Larsson,
Cosimo Cecchi, Dan Nicholson, Network Development, libc-alpha,
Rajalakshmi Srinivasaraghavan
Andy Lutomirski <luto@amacapital.net> writes:
> 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 guess you might want to follow the patch Raji sent today [1].
Her patch doesn't have all the syscalls you mentioned here, but has others too.
She will work to get a generic implementation for these functions.
[1] http://patchwork.sourceware.org/patch/7438/
--
Tulio Magno
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-07-01 16:19 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-06-30 21:14 Wiring up direct socket calls on x86_32 Linux? Andy Lutomirski
2015-06-30 21:29 ` Andreas Schwab
2015-07-01 16:19 ` Tulio Magno Quites Machado Filho
2015-07-01 16:19 ` Tulio Magno Quites Machado Filho
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.