ppll

Greg Kroah-Hartman

Linux kernel maintainer; runs the stable kernel releases and maintains the USB and driver core subsystems.

Greg Kroah-Hartman did not write this page. ppll compiled it from their own words, each linked to the source. Is this you? · Report a mistake

Follow

Latest GitHub

What they believe

The bold line is korrents’ wording; the quote is theirs. These 2: what they wrote before what they said aloud, one per source, newest first.

All 13 beliefs, on korrents

Everything, newest first — across every channel.

Sources

3 November

2 November

1 November

15 October

16 February

Greg Kroah-HartmanKorrents

From one piece Linux CVE assignment process 3 beliefs · kroah.com

2 January

Greg Kroah-HartmanKorrents

From one piece Linux kernel security work 2 beliefs · kroah.com

9 December 2025

Greg Kroah-HartmanKorrents

From one piece Linux kernel version numbers 3 beliefs · kroah.com

8 December 2025

4 November 2025

17 August 2025

The whole feed →

Beliefs

  • Korrents What they believe 13 beliefs — each backed by an exact quote.

    Each is a — compiled by korrents.com, not by them: the one-line wordings are korrents', the quotes are theirs.

    Recent

    Show 10 more
    • The current arrangement of the kernel security team may become the standard for project security teams due to the European Union's CRA law.
      This arrangement has allowed the kernel security team to remain independent and continue to operate across the different governments that the members operate in, and it looks to become the normal way project security teams work with the advent of the European Union's new CRA law coming into affect which places requirements on response time of companies that receive notice of potential security issues in their projects.

      Linux kernel security work Said 2 Jan 2026

      Full record — everyone who holds this →

      Europe

    • The 'no embargo' policy for kernel security is difficult to maintain when dealing with hardware and operating system cross-platform issues.
      As history has shown us with Spectre and Meltdown, this "no embargo" policy does not always work well when working with problems that cross operating systems and hardware platforms, possibly requiring firmware or microcode updates.

      Linux kernel security work Said 2 Jan 2026

      Full record — everyone who holds this →

    • All Linux kernel releases are stable and backwards compatible for userspace programs to all previous kernel releases.
      All releases are "stable" and backwards compatible for userspace programs to all previous kernel releases.

      Linux kernel version numbers Said 9 Dec 2025

      Full record — everyone who holds this →

      Linux

    • No kernel release should ever break an existing user's code or workflow.
      No kernel release should ever break any existing user's code or workflow.

      Linux kernel version numbers Said 9 Dec 2025

      Full record — everyone who holds this →

    • It is not safe to compare kernel branches against each other using simple version number comparisons to track fixes.
      It is NOT safe to do a simple "if this version number is bigger than the previous one, then all fixes for it will be in the next release." You have to treat each kernel "branch" as a unique tree, and not compare them against each other in order to be able to properly track changes over time.

      Linux kernel version numbers Said 9 Dec 2025

      Full record — everyone who holds this →

    • The CVE JSON format is much more complicated than the format used by the kernel community to track CVE assignments.
      document a way that people can track CVE assignments on their own in a format that is, in my opinion, much simpler than attempting to rely on the CVE json format (and don't get me started on NVD...)

      Linux CVEs, more than you ever wanted to know Said 8 Dec 2025

      Full record — everyone who holds this →

    • Supporting a kernel for 6 years requires constant testing by users of the kernels.
      The above is what I need in order to be able to support a kernel for 6 years, constant testing by users of the kernels.

      Helping Out With Lts Kernel Releases Said 3 Feb 2021

      Full record — everyone who holds this →

    • The best solution for most Linux users is to use the kernel provided by their favorite Linux distribution.
      The best solution for almost all Linux users is to just use the kernel from your favorite Linux distribution.

      What Stable Kernel Should I Use Said 24 Aug 2018

      Full record — everyone who holds this →

      Linux

    • Using older LTS releases in general computing environments with untrusted users or virtual machines is not recommended.
      These kernels are not to be used in any type of "general computing" model where you have untrusted users or virtual machines, as the ability to do some of the recent Spectre-type fixes for older releases is greatly reduced, if present at all in some branches.

      What Stable Kernel Should I Use Said 24 Aug 2018

      Full record — everyone who holds this →

    • The community cannot support companies that use unmaintained kernel releases.
      The community can not support you as no one is watching all kernel versions for specific issues, so you will have to rely on in-house support for everything that could go wrong.

      What Stable Kernel Should I Use Said 24 Aug 2018

      Full record — everyone who holds this →

    All 13 beliefs →

What is a korrent?

A korrent is a belief a person has stated in their own words: one sentence stating the claim, backed by a quote and a source, kept at korrents.com.

Under a name here, the quoted block is what they actually said. The korrent beneath it is the claim those words support, in korrents' wording — tap it to see the record, its source, and who else holds it.

Nobody here wrote their own korrents. They are compiled from public statements, and a person can change their mind, which is recorded too.

Recommends rcmnd

  • rcmnd What they recommend 13 things — each backed by an exact quote.

    Compiled by rcmnd.app, not by them: the quotes are theirs, and each links to the post it was copied from.

    Recent

    • Liked Nexus 7
      I also have a Nexus 7 tablet, which I'm finding I like more and more these days, and have given up my previous Kindle and iPad for it.

      usesthis.com 15 Nov 2012

      What others say about Nexus 7 →

    • Uses AWS
      Thanks to Amazon's generosity, I've been doing a lot more kernel build testing on their AWS systems, utilizing a 32 processor, 64Gb virtual machine, allowing me to build multiple kernels at the same time all on a RAM disk in minutes.

      usesthis.com 15 Nov 2012

      sponsored

      What others say about AWS →

    • Liked CyanogenMod
      My Nexus 7 tablet is running the nightly CyanogenMod releases and have had no problems at all with it.

      usesthis.com 15 Nov 2012

      What others say about CyanogenMod →

    Show 10 more

    All 13 recommendations →

Where they publish

About the English under a post

Some people here publish in a language other than English. Where they do, this site shows a machine translation beneath the post, in this typeface — the site's own, not theirs.

The post itself is never changed, moved or hidden: what is set in the serif above is exactly what the person published, and it is what to quote them on. A translation can be wrong in ways that matter, especially about tone.

Only the post's own words are translated. A quoted post, a linked article and a belief on korrents.com are left in their original language.