News for hackers. Stuff that matters.
Re:The Dirty Pipe Vulnerability by rfoo on Monday March 07, 2022 @08:30AM (#30587486)
Yes? This is faster and easier than you may think it to be. Building a reasonably small kernel only takes ~a minute. People usually have fully automated git-bisect-run scripts for build & test in qemu.
Re:The Dirty Pipe Vulnerability by bananabiscuit on Monday March 07, 2022 @08:38AM (#30587563)
Oh, interesting, did not know it could be so fast.
Re:The Dirty Pipe Vulnerability by gengkev on Monday March 07, 2022 @05:13PM (#30594043)
For me, at least, there's an important difference missing from the debate over the term "C/C++": compiling C code is always much faster than you would expect, but compiling C++ code is always much slower than you would expect...
Re:The Dirty Pipe Vulnerability by db48x on Friday March 11, 2022 @02:32PM (#30644913)
And yet there's an ongoing effort to optimize the kernel compile time by rearranging all of the headers. On a modern machine with plenty of cores a kernel build is pretty quick, but they're talking about slicing 20% or more off the top.

It's always slower than we'd like.

Re:The Dirty Pipe Vulnerability by cjbprime on Tuesday March 08, 2022 @03:58AM (#30597972)
Perhaps more importantly than being fast, it is scriptable. ("git bisect run" can take a shell command to run and interpret the exit code of, so you could script everything including the kernel recompiles and walk away for a few hours.)