← Back to team overview

kernel-packages team mailing list archive

[Bug 1562004] Re: S390: glibc does not use direct socket-syscalls, but the multiplexer-socket-syscall.


** Changed in: linux (Ubuntu)
     Assignee: Skipper Bug Screeners (skipper-screen-team) => Dimitri John Ledkov (xnox)

** Package changed: linux (Ubuntu) => glibc (Ubuntu)

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  S390: glibc does not use direct socket-syscalls, but the multiplexer-

Status in glibc package in Ubuntu:

Bug description:
  == Comment: #0 - Stefan Liebler <STLI@xxxxxxxxxx> - 2016-03-24 11:16:16 ==

  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"

  and the glibc commit:
  "S390: Call direct system calls for socket operations."

To manage notifications about this bug go to: