Skip to content

glibc-2.26-75#28622

Merged
vcunat merged 2 commits intostagingfrom
glibc-2.26
Nov 6, 2017
Merged

glibc-2.26-75#28622
vcunat merged 2 commits intostagingfrom
glibc-2.26

Conversation

@vcunat
Copy link
Copy Markdown
Member

@vcunat vcunat commented Aug 27, 2017

Largest expected caveat: upstream bumped the minimal supportable kernel to 3.2.0. That's the oldest kernel still supported upstream, released in Jan 2012, but most notably RHEL 6 and derivates still use a heavily patched 2.6.32 kernel and those systems are still supported and in use (production support is scheduled to last till the end of 2020!).

Therefore, I suggest to postpone this after branching 17.09, at least; it won't be nice even after that, but I fail to see a better option ATM.

@vcunat vcunat added this to the 18.03 milestone Aug 27, 2017
@mention-bot
Copy link
Copy Markdown

mention-bot commented Aug 27, 2017

@vcunat, thanks for your PR! By analyzing the history of the files in this pull request, we identified @edolstra, @peti and @Dridus to be potential reviewers.

@vcunat
Copy link
Copy Markdown
Member Author

vcunat commented Aug 27, 2017

A single coreutils test started failing :-/

test-getopt.h:754: assertion 'strcmp (argv[1], "donald") == 0' failed

It seems no use to rush merging this.

@vcunat vcunat mentioned this pull request Sep 2, 2017
Merged
8 tasks
@wizeman wizeman closed this Oct 30, 2017
@wizeman wizeman deleted the glibc-2.26 branch October 30, 2017 15:20
@grahamc grahamc restored the glibc-2.26 branch October 30, 2017 15:54
vcunat added 2 commits November 5, 2017 19:09
@vcunat
gcc6: fix build with new glibc, by upstream patches
0c01c58
@vcunat
glibc: 2.25-49 -> 2.26-75
9bb67d5 
Security: the NEWS claims a couple more CVEs are fixed than what we
patched, though perhaps nothing critical.

I personally don't find DNS fragmentation attacks that interesting
anymore, as it's just about weaker improvements for cases that choose
not to use DNSSEC.

Largest expected caveat: upstream bumped the minimal supportable kernel
to 3.2.0.  That's the oldest kernel still supported upstream, released
in Jan 2012, but most notably RHEL 6 and derivates still use a heavily
patched 2.6.32 kernel and those systems are still supported and in use
(production support is scheduled to last till the end of 2020!).
@vcunat vcunat changed the title [WIP] glibc-2.26 glibc-2.26-75 Nov 5, 2017
@vcunat vcunat reopened this Nov 5, 2017
@vcunat vcunat added the 1.severity: security Issues which raise a security issue, or PRs that fix one label Nov 5, 2017
@vcunat
Copy link
Copy Markdown
Member Author

vcunat commented Nov 5, 2017

Now there are some CVE fixes in this PR. I won't keep it waiting long, just let 17.09 rebuild first with glibc patches.

@GrahamcOfBorg GrahamcOfBorg added 10.rebuild-darwin: 101-500 This PR causes between 101 and 500 packages to rebuild on Darwin. 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-linux-stdenv This PR causes stdenv to rebuild on Linux and must target a staging branch. labels Nov 5, 2017
@vcunat vcunat mentioned this pull request Nov 6, 2017
Closed
8 tasks
@vcunat vcunat merged commit 9bb67d5 into staging Nov 6, 2017
vcunat added a commit that referenced this pull request Nov 6, 2017
@vcunat
Merge #28622: glibc-2.26
f245fe9
@vcunat vcunat deleted the glibc-2.26 branch November 6, 2017 12:05
@vcunat
Copy link
Copy Markdown
Member Author

vcunat commented Nov 7, 2017

Hmm, this will cause relatively lots of build-time breakages. I will try to patch some, mainly older versions of gcc and llvm, and anything blocking "important" packages, but I can't manage everything.

@vcunat
Copy link
Copy Markdown
Member Author

vcunat commented Nov 7, 2017

@7c6f434c, @asppsa: do you think that pure can be migrated to some newer llvm? So far I only bothered to fix 3.7 and newer branches...

@7c6f434c
Copy link
Copy Markdown
Member

7c6f434c commented Nov 7, 2017

Technical answer: still no, https://bitbucket.org/purelang/pure-lang/issues/36/port-pure-to-the-mcjit-in-order-to-support

@asppsa
Copy link
Copy Markdown
Contributor

asppsa commented Nov 8, 2017

@vcunat, yeah dependency on old LLVM is unfortunately an ongoing problem for Pure. My guess is that this will not be fixed any time soon.

@vcunat
Copy link
Copy Markdown
Member Author

vcunat commented Nov 8, 2017

OK. It's similar for llvm-general, though there are branches for newer LLVM versions.

@vcunat
Copy link
Copy Markdown
Member Author

vcunat commented Nov 8, 2017

I will probably fix llvm-3.5 within a week, but certainly feel free to beat me.

@vcunat vcunat mentioned this pull request Nov 9, 2017
Closed
@orivej orivej mentioned this pull request Nov 15, 2017
Closed
22 tasks
@phunehehe phunehehe mentioned this pull request Nov 17, 2017
Closed
@vcunat
Copy link
Copy Markdown
Member Author

vcunat commented Dec 21, 2017

Support for RHEL 6 and friends: #32954

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

1.severity: security Issues which raise a security issue, or PRs that fix one 10.rebuild-darwin: 101-500 This PR causes between 101 and 500 packages to rebuild on Darwin. 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-linux-stdenv This PR causes stdenv to rebuild on Linux and must target a staging branch.

Projects

None yet

Milestone

18.03

Development

Successfully merging this pull request may close these issues.

6 participants

@vcunat @mention-bot @7c6f434c @asppsa @wizeman @GrahamcOfBorg