With =sys-kernel/gentoo-sources-4.14.52 being stable and the only open bug for =sys-kernel/linux-headers being https://bugs.gentoo.org/648008 (which affects 4.15). I'd like to request toolchain to consider stabilization of at least =sys-kernel/linux-headers-4.14 As for some rationale for the request, a good reason might be the better ARM64 support pointed on https://bugs.gentoo.org/638848
Assigning to toolhcain as they are the ones that should send the stabilization request. I'm targetting 4.14 mostly because of the kernel stabilization but any higher version will work equally well.
(In reply to Francisco Blas Izquierdo Riera from comment #0) > With =sys-kernel/gentoo-sources-4.14.52 being stable and the only open bug > for =sys-kernel/linux-headers being https://bugs.gentoo.org/648008 (which > affects 4.15). I'd like to request toolchain to consider stabilization of at > least =sys-kernel/linux-headers-4.14 > > As for some rationale for the request, a good reason might be the better > ARM64 support pointed on https://bugs.gentoo.org/638848 While it should be fine to request linux-headers stabilization. It sounds like the only reason to stabilize linux-headers is kernel version. linux-headers don't have to be stabilized in lockstep with kernel: https://wiki.gentoo.org/wiki/Project:Toolchain/sys-kernel/linux-headers
Hi Slyfox! There are a few things that would require a new version of the headers: * The MSG_ZEROCOPY socket flag. * preadv2 support for RWF_NONBLOCK * madvise support for MADV_WIPEONFORK * Support for some new bpf jump instructions But to be sincere I'm not sure any of them grants a stable request, maybe the bpf one. I'm unsure what would happen if some program makes use of the new instructions but misses the .h file declarations for them.
Arches, please stabilize linux-headers targeting the following keywords: KEYWORDS="alpha amd64 arm arm64 hppa ia64 m68k ppc ppc64 s390 sh sparc x86" Most comprehensive test would be to check if there are regressions on a package list: https://gitweb.gentoo.org/proj/toolchain/linux-headers-patches.git/tree/testing.txt But practically if gcc, glibc and boot-loaders survive rebuild it should be good enough.
x86 stable
amd64 stable
Created attachment 558216 [details] boot.log (ppc64) Looking good on ppc64. Toolchain rebuild with linux-headers-4.14-r1 was successful. Rebuilding the packages from the testing.txt keyworded for ppc64 was successful. Rebooting went without problems.
Created attachment 558310 [details] boot.log (ppc) Looking good on ppc64. Toolchain rebuild with linux-headers-4.14-r1 was successful. Rebuilding the packages from the testing.txt keyworded for ppc64 was successful. Rebooting went without problems.
(In reply to ernsteiswuerfel from comment #8) > Created attachment 558310 [details] > boot.log (ppc) > > Looking good on ppc64. Erm, I mean ppc 32bit.
ppc/ppc64 stable thanks to ernsteiswuerfel!
sparc stable
ia64 stable
hppa stable
arm64 stable
s390/sh/m68k stable
arm stable
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b7527fde68f469ca8699931705844fdb9598abf1 commit b7527fde68f469ca8699931705844fdb9598abf1 Author: Tobias Klausmann <klausman@gentoo.org> AuthorDate: 2019-01-30 13:19:56 +0000 Commit: Tobias Klausmann <klausman@gentoo.org> CommitDate: 2019-01-30 13:19:56 +0000 sys-kernel/linux-headers-4.14-r1: alpha stable Bug: http://bugs.gentoo.org/660364 Signed-off-by: Tobias Klausmann <klausman@gentoo.org> sys-kernel/linux-headers/linux-headers-4.14-r1.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
We are done here.
