FEDORA-2018-884a105c04

security update in Fedora 26 for kernel

Status: stable a year ago

Update to v4.16.7 which contains fixes across the tree. This also temporarily reverts the fix for CVE-2018-1108 as it resulted in boots hanging in some scenarios.


Update to v4.16.6 which contains fixes across the tree


Update to v4.16.5 which contains fixes across the tree


Rebase to v4.16.4


The 4.15.18 stable kernel update contains a number of important fixes across the tree.

Reboot Required

After installing this update it is required that you reboot your system to ensure the changes supplied by this update are applied properly.

How to install

sudo dnf upgrade --advisory=FEDORA-2018-884a105c04

Comments 40

This update has been submitted for testing by jcline.

This update has obsoleted kernel-4.15.18-200.fc26, and has inherited its bugs and notes.

This update has been pushed to testing.

My chat server (a libvirt guest) seems to work just fine with this update.

karma: +1 critpath: +1

no regressions noted

karma: +1

jcline edited this update.

New build(s):

  • kernel-4.16.5-100.fc26

Removed build(s):

  • kernel-4.16.4-100.fc26

Karma has been reset.

This update has been submitted for testing by jcline.

This update has been pushed to testing.

works for me

karma: +1

works for me in a VM

karma: +1

works for me

karma: +1

jcline edited this update.

New build(s):

  • kernel-4.16.6-100.fc26

Removed build(s):

  • kernel-4.16.5-100.fc26

Karma has been reset.

This update has been submitted for testing by jcline.

Passed default and performance kernel tests on Intel C2D-6300 and i5-6600 platforms. MATE desktop and general performance seems normal. No regressions noted.

karma: +1 critpath: +1

This update has been pushed to testing.

Works fine in a VM.

karma: +1

jcline edited this update.

New build(s):

  • kernel-4.16.7-100.fc26

Removed build(s):

  • kernel-4.16.6-100.fc26

Karma has been reset.

This update has been submitted for testing by jcline.

What is the point of testing this? This is the FOURTH build in a row, the update has gotten positive karma eight times, for a grand total of currently zero. It has reached the stable threshold three times, only to be removed and reset all three times, and it's not even in testing yet. Would it be that difficult to push something out? https://en.wikipedia.org/wiki/Bait-and-switch

Hi @jag,

Previous kernels were in the testing repository and the testing people have provided is very valuable. This is a rebase from 4.15 to 4.16 so thorough testing is important. Unfortunately, there was an issue introduced in 4.16.4[0] that caused some systems to hang during boot. Rather that pushing out a kernel with a rather serious regression, I opted to wait a few days to see if we could learn more about the problem and get it fixed. I apologize if this has been frustrating. This build includes a work-around and I'm planning on pushing this to stable once it reaches the karma threshold.

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1572944

@jag if it works for you deploy it - guess what - 40 machines running still on F26 are on 4.16.x in production here and the machine in front of me is running the 4.16.7 build for F27 - you don't need for a package in question which works fine for you get moved to stable - your feedback and the feedback of others helps to minimize issues until the rebased kernel is pushed out to everybody

@hreindl Except no testers mentioned any issues, or gave negative karma, including the update it obsoleted. Only positive karma followed by removal and reset, and then rinse & repeat.

@jag WTF - not everybody is using bodhi and giving karma - one bugreport is even linked here - the decision pushing updates to stable is based on kown bugs and karma

@hreindl

"not everybody is using bodhi and giving karma" No, but some are, and you treat them very disrespectfully by ignoring their feedback and not communicating.

"one bugreport is even linked here" If you refer to #1572944, that wasn't mentioned until after the very latest (but maybe not the last, hmmmm?) build removal.

"the decision pushing updates to stable is based on kown[sic] bugs and karma" What I'm concerned with is the decision to not push to stable, but instead remove and reset without a word.

If you took half the energy you use on defending bad practices, and used it to improve the workflow, Fedora would be in a much better state. As it is, this update still has no karma, 4.16.7 for fc27 (until a few days ago the latest release) is not even in Bodhi yet three days after release, and the previous one for fc27 still has zero karma.

I've been using Fedora exclusively for almost ten years (since FC10), as I prepared to upgrade to FC28 I thought to myself "Why?". Instead I'll prepare to upgrade to Slackware. That gives the added bonus of not having Systemd shoved down my throat. Thank you for these years, I especially liked FC17 and FC21.

Rebases are always tricky. We ran into a major blocking issue with random number generation and the updates were delayed because of figuring out how to approach that. That should be fixed now so updates should be coming at a regular cadence.

@jag this update was still not in updates-testing as i trid yesterday "fedora-easy-karma" and so you confuse different issues, one is the shitty Fedora infrastructure which takes ages until things appear at least in updates-testing - and no i won't go to the bodhi website and do it manually because i have better things to do and wish all that fools giving karma for different packages than they have installed would disappear there too - also don't play the "i use Fedora so long" card because it's laughable when you where that late at the party

This update has been pushed to testing.

works for me

karma: +1

@samoht0 It sounds like that issue only occurs sometimes, is that correct, or can you reproduce it 100% of the time (and never reproduce it on 4.16.6)? The upstream bug report is still in the NEEDINFO state[0]. Could you please provide the requested information?

Thanks.

[0] https://bugzilla.kernel.org/show_bug.cgi?id=198855

Yes, it's random. As it might be a irq handling issue, timing might be related. It also looks like, it's more unlikely when hibernating after a fresh boot. Didn't break in two tries today. When I get some usable result till I install F28, I'll provide the requested info.

But as a matter of fact, it never broke with 15.17, 15.18, 16.4, 16.5 and 16.6. At least 25 resumes.

Seems to work on my chat server, which is a kvm guest.

karma: +1 critpath: +1

@jag why do you care about kernel packages for F26 when you are preparing for an upgrade to F28? How is Slackware working out for you?

no regressions noted, uptime more or less 48 hours

karma: +1 critpath: +1

Works on my machine.

karma: +1 critpath: +1

This update has been submitted for batched by jcline.

This update has been submitted for stable by jcline.

Thanks for testing!

This update has been pushed to stable.

Content Type
RPM
Status
stable
Test Gating
Submitted by
Update Type
security
Update Severity
unspecified
Karma
+2
stable threshold: 2
unstable threshold: -3
Autopush
Disabled
Dates
submitted a year ago
in testing a year ago
in stable a year ago
modified a year ago

Related Bugs 2

00 #1531927 lirc_zilog ceased working with kernel 4.14
00 #1571036 Kernel updates breaks screen brightness keys

Automated Test Results

Test Cases

00 Test Case kernel regression