Hacker News Reader

Comment by cmurf | Hacker News Reader

I'm not seeing the patch in 4.20.11's changelog or any of the longterm kernel versions posted today.

Inspecting the code in 4.20.11, I can confirm that the fix is NOT in there.

It's trivial to apply yourself, though from https://github.com/torvalds/linux/commit/9060cb719e61b685ec0...

    curl https://github.com/torvalds/linux/commit/9060cb719e61b685ec0102574e10337fa5f445ea.patch | git am

(Or `| patch -p1` if you don't have a git checkout of the kernel tree.)

I literally just compiled 4.20.11 for Slackware. I swear these things are popping up more often. Or more likely since spectre I've just been paying more attention

More people are fuzzing the kernel publicly, and with better tools.

syzkaller.appspot.com should give you an idea how many THOUSANDS of these types of bugs exist in the current ToT kernel

What is ToT? I’ve found that term mentioned several times on the Chromium bug tracker but no definition.

TOT = Tip of Tree.

Tip of Tree / Top of Tree. I.e present as of the most recent commit on the main development branch.

Yup. Kind of has my mind racing. And practically speaking, at that point, it feels like I need to employ a similar aggressive approach similar to our application. Go faster, and accept pain on the outer layer.

Maybe the answer is to do a daily automated recompilation of the kernel, rebuild of the edge LB and FW images followed by automated, staged rollout and rollback. If we're vulnerable anyway, let's just pick up the fixes from yesterday at least and roll back if things go wrong. That sounds really scary, but doable.

Reply on news.ycombinator.com