Public bug reported: == Comment: #0 - Stefan Liebler <[email protected]> - 2016-03-24 11:16:16 == Hi,
the glibc socket functions, like connect(), bind(), socket(), ... do currently use svc 102 (multiplexer-socket-syscall: see /usr/include/s390x-linux-gnu/asm/unistd.h: #define __NR_socketcall 102) The direct socketsyscalls are also available for s390 since kernel 4.3: #define __NR_connect 362 #define __NR_bind 361 #define __NR_socket 359 ... The kernel in my used ubuntu alpha is 4.4.0-15 and the glibc 2.23. This glibc release can use these direct socket-syscalls, if glibc is configured with "--enable-kernel=4.3.0". Or even better, use the kernel-level, which will be used in the first release for s390. Here is the kernel commit: "s390: wire up separate socketcalls system calls" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=977108f89c989b1eeb5c8d938e1e71913391eb5f and the glibc commit: "S390: Call direct system calls for socket operations." https://sourceware.org/git/?p=glibc.git;a=commit;h=016495b818cb61df7d0d10e6db54074271b3e3a5 ** Affects: ubuntu Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-139627 severity-high targetmilestone-inin1604 ** Tags added: architecture-s39064 bugnameltc-139627 severity-high targetmilestone-inin1604 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562004 Title: S390: glibc does not use direct socket-syscalls, but the multiplexer- socket-syscall. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1562004/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
