update kernel in release-16.03

[sorokin]

Currently the kernel in branch release-16.03 is not up to date. Could the following commits be cherry-picked from master into release-16.03?

commit 4489454
Author: Tim Steinbach tim@nequissimus.com
Date: Sat Oct 22 12:10:34 2016 -0400

linux: 4.4.26 -> 4.4.27

commit 1af5b2a
Author: Tim Steinbach tim@nequissimus.com
Date: Sun Oct 30 10:29:37 2016 -0400

linux: 4.4.27 -> 4.4.28

commit ef1a188
Author: Eelco Dolstra edolstra@gmail.com
Date: Tue Nov 1 11:31:00 2016 +0100

linux: 4.4.28 -> 4.4.30

[vcunat]

My understanding is that 16.03 is no longer maintained (and is likely to contain multiple vulnerabilities).

[sorokin]

Unfortunately I can not update to release-16.09 because of #18995 (see my comment #7220 (comment)). Until it is fixed I have to keep some commits cherry-picked on top of release-16.03. It would be great if some of them are applied upstream too.

BTW where can I find EOL dates for nixos releases? I tried to do this before submitting this bug report, but I didn't find it on neither the official site nor github.

[vcunat]

I think there's no real official announcement about EOL, but it's really lots of work to keep up with all those CVEs, and AFAIK contributors generally didn't want to do the work longer than a few weeks after a new stable release.

I picked linux-4.4.30. Just git cherry-pick -x suitable patches, and submit PR against release-16.03 (you can repeat once a while). Perhaps ping me, if noone merges it. The Hydra job should not be a problem, if given a lower priority; it's the manpower/motivation that is/was missing.

[domenkozar]

I announce EOL with new stable release, for example http://lists.science.uu.nl/pipermail/nix-dev/2016-October/021882.html

[vcunat]

Ah, thanks for correcting that.

[sorokin]

@domenkozar Thank you. I see now. I assumed this policy, but as some commits got into 16.03 after 16.09 was announced, I thought that probably this is not the case.

@vcunat Thank you. I will make a PR if I have any appropriate patches.