Upgrade to Linux 4.19.16-1 in 3.13
It got uploaded yesterday. Depending on when exactly we freeze, we might get it or not in 3.12~rc1 and 3.12. Let's make a conscious decision about it.
- Assignee deleted (
- Target version changed from Tails_3.12 to Tails_3.13
I think we should skip this kernel bump for 3.12; it's too little, too late. As for "too little", I compared buster (4.19.12 and Tails already uses 4.19.13) vs sid (4.19.16) and only two issues were listed as "vulnerable" for buster and "fixed" for sid, but they were actually fixed in 4.19.13 which we already install. And "too late" because I'm gonna prepare Tails 3.12~rc1 today, so being blocked on this ticket would probably delay the release another day.
- Subject changed from Consider Linux 4.19.16-1 for 3.13 to Upgrade to Linux 4.19.16-1 in 3.13
- Type of work changed from Research to Code
4.19.16 was uploaded to stretch-backports by benh, which is usually a good sign of maturity; also, it's been in sid since Jan 17 and we install it on our devel branch since a week. The only severe regression reported to Debian is https://bugs.debian.org/922028, which won't affect Tails. So I think we're good to go and should take this update, at least to get the bugfixes it brings (if not for security reasons, although it fixes a bunch of potential Spectre vulns).
Meanwhile, 4.19.20 is being prepared in the Vcs-Git; it bumps ABI to 3; it brings quite a few nice config improvements and it might be mature enough in time for 3.13, we'll see => #16458.