S390: glibc does not use direct socket-syscalls, but the multiplexer-socket-syscall.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glibc (Ubuntu) |
Won't Fix
|
Wishlist
|
Adam Conrad |
Bug Description
== Comment: #0 - Stefan Liebler <email address hidden> - 2016-03-24 11:16:16 ==
Hi,
the glibc socket functions, like connect(), bind(), socket(), ... do currently use svc 102
(multiplexer-
#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-
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:/
and the glibc commit:
"S390: Call direct system calls for socket operations."
https:/
tags: | added: architecture-s39064 bugnameltc-139627 severity-high targetmilestone-inin1604 |
Changed in ubuntu: | |
assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
affects: | ubuntu → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
assignee: | Skipper Bug Screeners (skipper-screen-team) → Dimitri John Ledkov (xnox) |
affects: | linux (Ubuntu) → glibc (Ubuntu) |
Changed in glibc (Ubuntu): | |
importance: | Undecided → Wishlist |
tags: |
added: targetmilestone-inin1804 removed: targetmilestone-inin1604 |
Changed in glibc (Ubuntu): | |
milestone: | ubuntu-16.04 → none |
Assigning to glibc maintainer