Profile cover photo
Profile photo
Greg Kroah-Hartman
About
Posts

Post has shared content
What he said :)
Despite what various news sites out there may have told you, kernel 4.14 LTS is not planned to be supported for 6 years. Just because +Greg Kroah-Hartman‚Äč is doing it for 4.4 does not mean that all LTS kernels from now on are going to be maintained for that long.

It is possible that someone may pick up maintainership of 4.14 after Greg is done with it (it's happened in the past on multiple occasions), but you should emphatically not plan on that.

Your ultimate guide for the projected EOL for all LTS kernels is this page:

https://www.kernel.org/releases.html

Any resource that contradicts that page is wrong.

Post has attachment
Which version of GPL version 2 are you using for your project? There's so many to choose from!

Great bunch of research here from Philippe Ombredanne of nexB.

Post has attachment
Sometimes a name is just too good to pass up using...

Stable kernels are now released, go upgrade!
Photo

Post has attachment
It's been great to see Wireguard mature over the years into something that works really well. This past week it survived the LinuxCon/ELCE/Kernel Summit traffic thanks to +Konstantin Ryabitsev and packet.net setting up a server for us to use.

Then yesterday a few of us did a "code walkthrough" of the wireguard kernel codebase, displaying it on a large screen and walking through the various functionality "here's the receive path, here's the transmit path, here's the cookie handling, etc." which was really informative and highly recommended. I could only stick around for 4 hours, but I saw the main portions, and the other participants finished out the rest a few hours later.

Now I'm trying out a "commercial" vpn who is offering wireguard nodes, to see how well that works out. So far it's just so much simpler to configure and run than any OpenVPN client so on that point alone it's worth it.

Hopefully after the networking conference next week there will be a clearer roadmap for merging it into the kernel tree. The crypto code in the kernel module will probably have to play nicer with the in-kernel crypto apis, which is to be expected, but really, the current in-kernel crypto apis do need a serious revamp one of these days, no wonder Jason wrote his own interface...

Post has attachment
For some reason, seeing Linux in my clothes washer just made the whole "total world domination" thing more real.

And kudos to Samsung for making it easy to get the source code. Of course, I'll keep the machine off of the network, just to be safe :)
Photo

Post has attachment
Two achievements in one...
Photo

Post has attachment
A new file for the kernel's Documentation directory explaining how we feel our copyright should be enforced.

If lkml.org isn't up and running (it's a flaky box), here's a copy of my pull request that should provide you will all of the needed information about this file:

-------------
Documentation: Add a file explaining the requested Linux kernel license enforcement policy

Here's a pull request to add a new file to the kernel's Documentation directory.
It adds a short document describing the views of how the Linux kernel community
feels about enforcing the license of the kernel.

The patch has been reviewed by a large number of kernel developers already, as
seen by their acks on the patch, and their agreement of the statement with
their names on it. The location of the file was also agreed upon by the
Documentation maintainer, so all should be good there.

For some background information about this statement, see this article
written by some of the kernel developers involved in drafting it:
http://kroah.com/log/blog/2017/10/16/linux-kernel-community-enforcement-statement/
and this article that answers a number of questions that came up in the
discussion of this statement with the kernel developer community:
http://kroah.com/log/blog/2017/10/16/linux-kernel-community-enforcement-statement-faq/

If anyone has any further questions about it, please let me, and the TAB
members, know and we will be glad to help answer them.
-------------

And here's a link to the patch itself with the initial set of acks and the document, and the developers who agree with it.
https://lkml.org/lkml/2017/10/16/131

Post has attachment
I think I found my new office location...
Photo

Post has attachment
My Kernel Recipes talk about the "Linux kernel release model" is now up. Watch at the end as I crash two phones with a userspace program because they were not up to date.

My slides are also online, and can be found at:
https://kernel-recipes.org/en/2017/talks/linux-kernel-release-model/
where you can see Brendan Gregg's excellent talk as well.

Post has attachment
Wait while more posts are being loaded