This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug network/19682] s390x: Incorrect syscall definitions cause breakage with Linux 4.3 headers
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 25 Feb 2016 14:46:17 +0000
- Subject: [Bug network/19682] s390x: Incorrect syscall definitions cause breakage with Linux 4.3 headers
- Auto-submitted: auto-generated
- References: <bug-19682-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19682
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #3 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Florian Weimer from comment #2)
> (In reply to Stefan Liebler from comment #1)
> > I suggest to remove only the direct socket-syscalls in s390-64/syscalls.list
> > for older glibc-versions.
>
> This is what I did in Fedora 23 and 22 (based on glibc 2.22 and glibc 2.21).
> The Fedora 22 update has still not been released, but the Fedora 23 update
> works well (at least there haven't been any angry complaints).
>
> > Which glibc releases should get the backport or are still maintained?
> > 2.22, 2.21, ...?
>
> Sorry, no idea. 2.22 and 2.21 still have active stable branches. 2.19 is
> used by Debian jessie. But beyond that, I don't know.
The distro maintainers should be contacted for such a list:
https://sourceware.org/glibc/wiki/MAINTAINERS#Distribution_Maintainers
--
You are receiving this mail because:
You are on the CC list for the bug.