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

Post has attachment
Early morning walk to bcc in Berlin
Photo

Post has attachment
Another in the never-ending series of "where was that kernel released at?"

Today's installment is brought to you from 3/4 the way up of the tallest building in Taiwan. One of the best views I've ever had for this task. Not the first time it has happened here, and hopefully not the last.

Oh, and go upgrade, new kernels are out there, something for everyone:
4.4.54
4.9.15
4.10.3
Photo

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

Wait while more posts are being loaded