News for hackers. Stuff that matters.
Re:Red Hat reports security issue in Linux Kernel which was ... by baggy_trough on Tuesday June 23, 2020 @12:54PM (#23616606)
Why don't Red Hat et al use the LTS kernels?
Re:Red Hat reports security issue in Linux Kernel which was ... by gregkh on Tuesday June 23, 2020 @01:13PM (#23616959)
They feel like they know better and do not want all of the fixes that the LTS kernels provide for some crazy reason.

I suggest you contact them if you rely on a RHEL kernel to ask them why they do this, it's always seemed crazy.

Note, I'm the person who does the LTS kernel releases, maybe they just don't like me :)

Re:Red Hat reports security issue in Linux Kernel which was ... by rwmj on Tuesday June 23, 2020 @01:42PM (#23617429)
I'm certain that Red Hat and our kernel developers have no animosity towards you, in fact it's completely the opposite. You're well known in the community not just for this but for maintaining and writing countless drivers and loads of other great work in the kernel.

Fedora does use the LTS kernels.

Re:Red Hat reports security issue in Linux Kernel which was ... by iforgotpassword on Tuesday June 23, 2020 @02:06PM (#23617798)
> They feel like they know better and do not want all of the fixes that the LTS kernels provide for some crazy reason.

It's even crazier; they sometimes backport changes to their kernel that the LTS kernels don't get. We use a custom kernel module that contains a bunch of #if #endif blocks that check the kernel version for stuff that changed. Doesn't work on RedHat since you actually need the branch that's for more recent kernels in some places.

Re:Red Hat reports security issue in Linux Kernel which was ... by orf on Tuesday June 23, 2020 @02:11PM (#23617882)
Isn’t the whole autoconf stuff supposed to avoid the need for if macro soup, by using feature detection?
Re:Red Hat reports security issue in Linux Kernel which was ... by iforgotpassword on Tuesday June 23, 2020 @02:18PM (#23617991)
There would be cleaner ways to achieve this, maybe not specifically autoconf since I think that's more tailored towards "normal" (user space) stuff.

Macros are convenient to quickly check the version in your code without adding another layer of tooling... Until you end up with said macro soup of course.

It's actually a legacy module we're about to phase out for 5.x so don't worry too much. The new and shiny replacement will probably use git branches for whenever something changes.

Re:Red Hat reports security issue in Linux Kernel which was ... by stonogo on Tuesday June 23, 2020 @01:44PM (#23617466)
It could also be motivated by the fact that it's not entirely wise to base an entire multibillion dollar business around whatever text a non-employee happens to push to a repo you don't control.
Re:Red Hat reports security issue in Linux Kernel which was ... by gregkh on Tuesday June 23, 2020 @01:49PM (#23617541)
Android doesn't seem to mind, they require the LTS updates to be taken for their devices (well, "require" is a strong word, they are pushing harder now than they were in the past, "required" will be happening in the future, hopefully...)

As the number of systems running RHEL is really just a rounding error compared to the number of Android systems out there, maybe it doesn't really matter :)

Re:Red Hat reports security issue in Linux Kernel which was ... by bonzini on Tuesday June 23, 2020 @03:49PM (#23619320)
Android and RHEL are completely different scenarios.

The target of Android, which is who Google has to deal with, is multiple manufacturers creating kernels for custom hardware (often without upstream drivers), with very short product life, relatively little experience with upstream contribution and few needs for new features for a given major release of Android.

RHEL is developed by a single company with a 10 years life cycle, only 3-4 kernel versions to juggle but almost non-overlapping lifecycle (as far as the initial development-heavy phase is concerned). Development occurs upstream first and quite a few engineers are upstream developers or maintainers, so that the number of non-upstream features is very small and almost going down over time, see for example stuff like the secure boot lockdown patches that Matthew Garrett started when he was at Red Hat. And even though the product is not the kernel, we need to backport more features than what goes into LTS, because userspace needs them (user namespaces, driver updates, networking or virtualization optimizations, enablement for new processors, etc.)

So it's only natural that there are completely trade-offs to make.

Re:Red Hat reports security issue in Linux Kernel which was ... by azinman2 on Tuesday June 23, 2020 @02:14PM (#23617931)
I would guess that RHEL has more stringent requirements than your average me-too Android manufacturer.
Re:Red Hat reports security issue in Linux Kernel which was ... by radiator on Tuesday June 23, 2020 @02:20PM (#23618022)
But do the devices running Android generally operate with the same requirements as the servers running RHEL?
Re:Red Hat reports security issue in Linux Kernel which was ... by nordsieck on Tuesday June 23, 2020 @03:02PM (#23618614)
> But do the devices running Android generally operate with the same requirements as the servers running RHEL?

I guess it depends on the device and the business.

How many days of downtime on Amazon.com is the cost of bricking 1M phones? Or 100M?

Re:Red Hat reports security issue in Linux Kernel which was ... by stonogo on Tuesday June 23, 2020 @04:16PM (#23619658)
Yes, that's why all the servers in the datacenter are running Android, which has a stellar security record.

This sort of myopia is yet another excellent reason for Red Hat to take their kernel process in-house.

Re:Red Hat reports security issue in Linux Kernel which was ... by phh on Wednesday June 24, 2020 @02:19AM (#23624698)
LTS' security record is definitely not to be proven. The example we're currently commenting on this thread is only one occurence. It is highly re-occuring.

RHEL fixes only CVEs. Linus Torvalds consider there is no such thing as a security bug, that actually every bug is a security bug. So RHEL's kernel can't be secure.

Re:Red Hat reports security issue in Linux Kernel which was ... by zozbot234 on Tuesday June 23, 2020 @03:54PM (#23619387)
Debian also uses LTS-series kernels for their stable release - with their own patches on top. They don't actively backport features like RHEL does however.
Re:Red Hat reports security issue in Linux Kernel which was ... by baggy_trough on Tuesday June 23, 2020 @03:23PM (#23618930)
Why doesn't that argument apply to the mainline kernel?
Re:Red Hat reports security issue in Linux Kernel which was ... by Conan_Kudo on Tuesday June 23, 2020 @01:28PM (#23617214)
Note that Red Hat, SUSE, and Canonical all don't use them. They maintain their own kernel trees with their modifications. These kernel teams have different priorities:

* stable ABI within a timespan (RH, SUSE)

* feature backports based on customer demand (all three)

* out of tree goop (Canonical)

I've also heard from others (though notably, not folks specifically at these companies) that longterm kernels are iffier than regular stable kernels because people come out of the woodwork to push weird stuff for longterm kernels, which destabilizes things more than with regular stable kernels.

Re:Red Hat reports security issue in Linux Kernel which was ... by bluedays on Tuesday June 23, 2020 @01:33PM (#23617286)
Seems like even Arch maintains it's own kernel. Not uncommon for distros to do it at all.
Re:Red Hat reports security issue in Linux Kernel which was ... by artistsvoid on Tuesday June 23, 2020 @01:49PM (#23617549)
Wrong, or at the least misleading.

What do you mean by 'maintain' here? Because Arch is trying to stay on the bleeding edge side of things in a reasonable manner and is rolling release, they almost stay 1:1 with upstream, "maintains its own kernel" makes it sound like they would do some heavy patching and do active maintenance with certain kernel versions, et cetera. You can have a look yourself if you want to https://git.archlinux.org/linux.git/commit/?h=v5.7.5-arch1&i...

Re:Red Hat reports security issue in Linux Kernel which was ... by bluedays on Tuesday June 23, 2020 @02:40PM (#23618323)
They have their own kernel as can be seen here:

https://i.imgur.com/jP6Pdvq.png

Also if you look at the diffstat you can see that there were a number of changes here:

https://i.imgur.com/J2em78v.png

It may be align with the majority of the kernel, but these patches exist in every version of the kernel that is released by Arch.

What else could that be called aside from maintaining your own kernel?

These changes are extremely small within scope which is the nature of Arch, but they still exist. A more hands-on distro will see many more changes than Arch, naturally. However, as evidenced from the above you can see that Arch does have it's own kernel and I cited Arch as an example because it strives so hard to maintain 1:1 with upstream.

Btw, I use Arch.

Re:Red Hat reports security issue in Linux Kernel which was ... by phh on Tuesday June 23, 2020 @02:46PM (#23618388)
"maintaining your own kernel" in this context means that you're bringing bugfixes (including security) independently from the mainline Linux kernel, which would usually involve cherry-picking commits from the mainline.

Archlinux doesn't do that, and straight merges Linux mainline.

Re:Red Hat reports security issue in Linux Kernel which was ... by bonzini on Wednesday June 24, 2020 @02:04AM (#23624610)
The RHEL8 kernel has a few tens of thousands of commits on top of 4.18. That's a bit more than Arch. :)
Re:Red Hat reports security issue in Linux Kernel which was ... by fomine3 on Wednesday June 24, 2020 @01:16AM (#23624359)
Because release schedule doesn't match to LTS release schedule? Distributors may want to ship OS with latest kernel than latest LTS.
Re:Red Hat reports security issue in Linux Kernel which was ... by baggy_trough on Tuesday June 23, 2020 @01:39PM (#23617393)
What is the difference between a "longterm kernel" and a "regular stable kernel"?
Re:Red Hat reports security issue in Linux Kernel which was ... by gregkh on Wednesday June 24, 2020 @09:34AM (#23627683)
"regular stable kernel" lives only about 3-4 months, just long enough for the next release from Linus to feel "good enough".

"longterm kernel" lives for 2+ years. I pick one each year (usually the last one released in a year) for that.

See the releases page on kernel.org for details on what the longterm kernels are, and for how long they are being maintained and by whom.

Re:Red Hat reports security issue in Linux Kernel which was ... by iforgotpassword on Tuesday June 23, 2020 @02:09PM (#23617860)
Not in my experience. LTS never seems to break any compatibility, even internal kernel structs, function names, etc.
Re:Red Hat reports security issue in Linux Kernel which was ... by phh on Tuesday June 23, 2020 @02:43PM (#23618346)
Actually LTS does break ABI, but gregkh is working with Android to make a partially ABI-stable LTS (I assume it would be a fork of the real LTS though?).

I know they are also working with RH and Suse, but I don't know if RH and Suse will only share the tools, or will also have the same LTS source tree.

When I say "partially-ABI" stable, their goal is to list acceptable symbols and automatically verify that vendor modules use those symbols, and only those accceptable symbols are ABI-stable.

Re:Red Hat reports security issue in Linux Kernel which was ... by gregkh on Wednesday June 24, 2020 @09:33AM (#23627668)
That "partially-ABI stable" is the same exact thing that Red Hat and SUSE and Debian have been doing for 20+ years now. Nothing major and exciting there, but see the presentations at the Linux Plumbers conferences for details on the tools being used if people are curious (hint this time everyone is working together on the same set of tools...)
Re:Red Hat reports security issue in Linux Kernel which was ... by drewg123 on Tuesday June 23, 2020 @03:24PM (#23618940)
RHEL maintains a KABI to support binary device drivers. Given how frequently the linux kernel changes internal APIs, this would be much harder or even impossible if they changed kernel versions regularly.

Instead, they take features and bugfixes from upstream and merge them back into their kernel version, auditing them for changes that would not be binary compatible.

Re:Red Hat reports security issue in Linux Kernel which was ... by gulikoza on Tuesday June 23, 2020 @01:15PM (#23616998)
Red Hat sometimes also backports new features, not just security fixes. In the first years of RHEL life cycle new features and certain upgrades are usually added to the point releases. This is actually nicer than being locked into same feature kernel for 10 years...for those that can't afford the changes, you have the Extended Support for each point release which then gets only the security fixes.
Re:Red Hat reports security issue in Linux Kernel which was ... by heavyset_go on Tuesday June 23, 2020 @03:28PM (#23619012)
Ubuntu does the same thing. I'm only pointing it out because if you can't find a reason RH does it, you might be able to find the reason Canonical does it, though.
Re:Red Hat reports security issue in Linux Kernel which was ... by pjmlp on Tuesday June 23, 2020 @01:03PM (#23616787)
Probably drivers.
Re:Red Hat reports security issue in Linux Kernel which was ... by bubblethink on Tuesday June 23, 2020 @01:08PM (#23616880)
What about them ? I don't think the OP means using the upstream kernel directly, just why they don't use the same version as the LTS version.
Re:Red Hat reports security issue in Linux Kernel which was ... by tssva on Tuesday June 23, 2020 @03:03PM (#23618630)
Reasons I can think of include:

Not wanting to be tied to a kernel LTS release cycle you don't control.

The need to backport features and hardware enablement to the LTS kernel significantly offsets some of the benefits of using a LTS kernel.

The length of support for LTS kernels is significantly shorter than Redhat's length of support which means they would end up supporting it on their own for a significant timeframe anyways.