Profile cover photo
Profile photo
Greg Kroah-Hartman
About
Greg's posts

Post has attachment
Oh look, a new phone nice! Oh wait, 3.4 based kernel?

And an out-of-date 3.4 kernel at that? Go read the comments, Willy shows that this is a totally insecure device, over 5000 bug and security fixes are missing from the kernel.

Not good at all, something needs to be done for this issue, educating people and companies seems to be my full-time job these days...

Post has shared content
The coreOS people have much longer beards than the BSD people here at FOSDEM.

Post has attachment
Wireguard talk at +FOSDEM​. Good stuff, 4k lines of kernel code, half the size of your serial port driver.
Photo

Post has attachment
Releasing kernels during the standing-room-only opening talk at FOSDEM 2017.

Go get 4.4.47 and 4.9.8 now!
Photo

Post has attachment
Calm before the storm, FOSDEM....
Photo

Post has attachment
From an unnamed friend on Facebook, figured it was worth posting here as well... And if you wish to do your own, have at it: http://hepwori.github.io/execorder/ 
Photo

Post has attachment
Yes, 4.9 is the next longterm kernel. I've been saying that for a while, but somehow if it wasn't on the kernel.org website, no one believed me :)

Post has attachment
Have you ever wondered just how many lines of code your running kernel is using? Well, time for a dumb script that parses .c and .h files with sed!

Yeah, it's a horrid hack, but it's fun to get an idea of just how many lines of the 22 million included in the kernel tree that you rely on.

Build a kernel, and then go into the directory and run the script. Yeah, I should add an option to handle cross-builds better where the .o files are in another directory, feel free to send me patches...

For an example, my laptop, with a slimmed down configuration to only include the hardware I use, plus some drivers I test-build for:

~/linux/gregkh $ ~/linux/scripts/count_lines
Finding files for arch x86
Finding all .c files used based on the .o files...
Searching for what .h files the .c code pulls in...
Searching for what .h files the .h files pull in...
C: 2910 files 1716784 lines
H: 2232 files 419425 lines
Totals: 5142 files 2136209 lines

For my 4.9-stable allmodconfig test builds:
~/linux/stable/linux-4.9.y $ ~/linux/scripts/count_lines
Finding files for arch x86
Finding all .c files used based on the .o files...
Searching for what .h files the .c code pulls in...
Searching for what .h files the .h files pull in...
C: 23584 files 12485681 lines
H: 7948 files 820944 lines
Totals: 31532 files 13306625 lines

And finally, the defconfig for a Pixel phone:
~/linux/tmp/android_common $ ~/linux/scripts/count_lines arm64
Finding files for arch arm64
Finding all .c files used based on the .o files...
Searching for what .h files the .c code pulls in...
Searching for what .h files the .h files pull in...
C: 3312 files 2779211 lines
H: 2658 files 472081 lines
Totals: 5970 files 3251292 lines


Post has attachment
Saving here primarily as I keep sending this link to others in private email threads, but everyone in the Computer Science "industry" should look at this list, it's really good.

I think the best thing here is the "N-system" problem, where people somehow think that if you give a specification to N numbers of different groups, they will come up with N different implementations that can be then compared against each other in order to provide a "safe" system (i.e. run all 3, compare the results of the output, and if they differ, you know something went wrong somewhere.)

Turns out us programmers all end up making almost the same mistakes, so those "independent" systems almost always end up with the same bugs!

It also turns out that people really don't like being proven wrong about their ideas, so they keep saying that the "N-system" design is a secure one and should be used in new devices (cars, airplanes, etc.) The rebuttal to the critics is one of the best "stop going around and lying about our work" academic response I've read in a long time.

Lots of good reading for a winter weekend here, highly recommended.

Post has attachment
Best speaker gift ever, 6 pack of homebrew. It's as if they want me to come back and talk to them again!
Photo
Wait while more posts are being loaded