Linus Finally Releases Linux 4.15 Kernel, Blames Intel For Delay (phoronix.com)
An anonymous reader writes: Linus Torvalds has released Linux 4.15 following the lengthy development cycle due to the Spectre v2 and Meltdown CPU vulnerability mitigation work. This update comes with many kernel improvements including RISC-V architecture support, AMDGPU Display Code support, Intel Coffee Lake graphics support, and many other improvements.
"This obviously was not a pleasant release cycle, with the whole meltdown/spectre thing coming in in the middle of the cycle and not really gelling with our normal release cycle," Linus writes. "The extra two weeks were obviously mainly due to that whole timing issue... [T]he news cycle notwithstanding, the bulk of the 4.15 work is all the regular plodding 'boring' stuff. And I mean that in the best possible way. It may not be glamorous and get the headlines, but it's the bread and butter of kernel development, and is in many ways the really important stuff.
"Go forth and play with it, things actually look pretty good despite everything. And obviously this also means that the merge window for 4.16 is open... Hopefully we'll have a _normal_ and entirely boring release cycle for 4.16. Because boring really is good."
"This obviously was not a pleasant release cycle, with the whole meltdown/spectre thing coming in in the middle of the cycle and not really gelling with our normal release cycle," Linus writes. "The extra two weeks were obviously mainly due to that whole timing issue... [T]he news cycle notwithstanding, the bulk of the 4.15 work is all the regular plodding 'boring' stuff. And I mean that in the best possible way. It may not be glamorous and get the headlines, but it's the bread and butter of kernel development, and is in many ways the really important stuff.
"Go forth and play with it, things actually look pretty good despite everything. And obviously this also means that the merge window for 4.16 is open... Hopefully we'll have a _normal_ and entirely boring release cycle for 4.16. Because boring really is good."
... intel.
It little behooves the best of us to comment on the rest of us.
Has the systemd problem been fixed? I used to use Linux extensively, but I had to stop after systemd caused me way too many problems.
I've since moved to FreeBSD, and it has been an excellent experience. I really haven't missed Linux at all.
That said, I would consider using Linux again, but only if systemd is not involved in any way. Archaic distros like Slackware, or ones that require too much hand-holding like Gentoo, or hobbyist projects like Devuan just aren't options. It has to be real distros like Debian and Ubuntu that don't use systemd any longer.
It doesn't matter how much the kernel improves if systemd causes problems and ruins the user experience otherwise.
Linus himself should take a bigger role in pushing for the elimination of systemd.
we're-glad-youre-home-the-russians-pooped-in-the-hallway.jpg
He blames the Meltdown/Spectre mess in general (duh!), but he only blames the timing, which is either the discoverer's fault, or Microsoft's: the embargo was timed to coincide with patch Tuesday.
While the root cause may be placed at Intel's door, the timing of the disclosure after 10+ years of vulnerability is hardly Intel's choice, and Linus (correctly) refrains from linking them to it in any way.
Maybe it was the lack of intel on Intel's part for playing the wrong moves (risk v. profit) when they were faced with a showstopper
You must have missed the /. article about Linus throwing shade on intel for their shitty garbage (his words) code they wanted Linus to add to the kernal.
when Linux 4.15 is released? Aside from a few nerds that is. I mean come on. Its 2018 and Linux still only makes up, what, 1% of desktops? 75% of that being teens who hate M$?
Like seriously nobody cares. Even Linus knows, thats why he throws a bitch fit every couple weeks, its the only way for him and his irrelevant namesake OS can remain somewhat relevant.
Stop with the whiny editorializing in the headlines. Headlines are for facts, not for your opinion about how long it should take people who do real work to do it.
I guess he got tired of systemd trying to take over the kernel.
Imagine what they would come up with... faster than light travel or something like that im sure. Seriously, Imagine what a group of these fine folks could do.... save our fucked up world maybe.
[($)]
Headlines are for creating an emotional reaction in people to make them more likely to click on the article to read and/or comment. Guess who it worked on?
prima donna8s, and
tHIS iS wHY wINDOWS uSERS aRE winners!
This kernel release was not delayed by two weeks because Linus had to write a smack-down email. So, no.
I thought everyone in the super-fun-secret club knew about Spectre and Meltdown like 6 months ago, because it took them time to code up fixes? I'm guessing Linux kernel devs weren't part of the super-fun-secret club?
In general, Linux devs happens to have been working for a general class of technology (KAISER, now KPTI) that happens to also be useful against Meltdown (in addition to tons of other problems).
So from the perspective of Linux devs, not much changed (and it is the general mantra in team Linus Torvalds, that *any* bugs is a serious bug, no matter if it is a security one or not - so it's a general tendency that when there are security reports, it's business as usual).
The problem comes from the answer of the manufacturers :
- intel botched patches they were submitting (see Linus' ire about them), intel provided buggy firmware (CPU microcode) that causes problems and that Dell and HP ended-up delaying. Intel has tried to enable Meltdown circumvention for everyone even if they're almost the only constructor that's concerned, etc.
- AMD still can't really decide if version 2 of Spectre (abusing the indiredct branch prediction) can actually lead to an actual usable exploit in the wild or not. Though they at least now have determined that a few of their CPUs (since Zen, I think) are affected. So at least for now it's "enable retpoline for them, too".
etc.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
Using a Windows 7 machine myself, I am not aware of being protected by any Microsoft patch or anything re. Spectre and Meltdown attacks, which afaik can be used to remotely read off passwords in plaintext as they are typed in.
Are all governments now collecting passwords from users that maybe aren't even protected, and maybe never will be?
What kind of protection is there now? My impression is that server owners gets to have patches, but not the regular PC user.
Bios update?
OS update?
Cpu firmware update?
And I don't see how I can even trust Intel's ME in the first place.
I'm quite aware that he has complaints about Intel, but they're about other issues, particularly Intel's mitigation strategies for future processors. None of it relates to the 4.15 release schedule, and none of it was mentioned in the release announcement.
9-11 was a Jew job
I think the whole Spectre Meltdown thing will sell a ton of PC's when new chips hit the market that address this threat with hardware fixes. One has to wonder if this isn't the end result in the first place to increase PC sales? Think about it, even the fixes are a bitter pill to swallow. The only fix will be a new CPU. I just find that interesting that in 10 years of a flaw, its only exposed at a time when the PC market needs a infusion of buyers.
Yep... always everyoneâ(TM)s fault. Never his. Finger points outwards...
The Linux Weekly News usually has some pretty good information about kernel changes.
The most recent release requires a subscription, however all others are free to read.
Anythings possible... kinda scary.
[($)]