When you finish celebrating Linux turning 30, try new Linux 5.14, says Linus Torvalds
- Reference: 1630282304
- News link: https://www.theregister.co.uk/2021/08/30/linux_5_14/
- Source link:
"So I realize you must all still be busy with all the galas and fancy balls and all the other 30th anniversary events, but at some point you must be getting tired of the constant glitz, the fireworks, and the champagne," wrote Torvalds in his weekly [1]state of kernel development update . "The celebrations will go on for a few more weeks yet, but you all may just need a breather from them. And when that happens, I have just the thing for you – a new kernel release to test and enjoy. Because 5.14 is out there, just waiting for you to kick the tires and remind yourself what all the festivities are about.
"Of course, the poor tireless kernel maintainers won't have time for the festivities, because for them, this just means that the merge window will start tomorrow. We have another 30 years to look forward to, after all.
[2]
"But for the rest of you, take a breather, build a kernel, test it out, and then you can go back to the seemingly endless party that I'm sure you just crawled out of."
[3]Happy birthday, Linux: From a bedroom project to billions of devices in 30 years
[4]30 years of Linux: OS was successful because of how it was licensed, says Red Hat
[5]Google: Linux kernel and its toolchains are underinvested by at least 100 engineers
For those who decide that kernel testing is more fun than galas and balls and champagne, Linux 5.14 offers many tasty little tidbits.
Perhaps the most significant are memfd_secret and core scheduling because both are ongoing clean-up work to mitigate Intel's Spectre and Meltdown fiascos.
[6]
[7]
memfd_secret lets applications create an area of memory that only that application can access. Not even the kernel can access the designated area of memory. Which matters, because Spectre and Meltdown meant cached data could be accessed. memfd_secret is designed to provide a safe place for secrets like cryptographic keys or passwords to reside.
The new core scheduling code matters because one way to mitigate Spectre and Meltdown was to disable hyper-threading. Linux can now allow hyperthreading more efficiently and ensure that trusted and less-trusted workloads don't share a core and create potential Spectre-esque risks. This one's mainly for hyperscale operators – but seeing Linux is widely used by those players the update will have wide applicability.
[8]
And for now let's not worry that Intel just introduced a bunch more [9]pre-emptive execution tricks in its new architectures.
Speaking of Intel, version 5.14 of the kernel adds more support for Chipzilla's Alder Lake platform that puts multiple core types onto a single die and prioritises workloads depending on their needs.
Support for the RISC-V architecture was enhanced, giving it more access to some core kernel features such as the "transparent hugepages" memory mapping facility. The inclusion of SimpleDRM improves GPU-handling (DRM in this instance stands for Direct Rendering Manager).
[10]
Dell has contributed a driver allowing hardware-level disablement of webcams and microphones, to enable either actual kill switches or keypress combos that do the same in some of its laptops.
As promised, [11]legacy IDE has had its day and the Raspberry Pi 400 has been granted full support.
There's stacks more, of course, all available [12]here , or wherever good kernel downloads are made available. ®
Get our [13]Tech Resources
[1] http://lkml.iu.edu/hypermail/linux/kernel/2108.3/05438.html
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YSxX-6NPwYYeeG8pI@P08gAAAIc&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://www.theregister.com/2021/08/25/linux_kernel_30_years_old/
[4] https://www.theregister.com/2021/08/25/30_years_of_linux_red_hat/
[5] https://www.theregister.com/2021/08/04/google_linux_kernel_security/
[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YSxX-6NPwYYeeG8pI@P08gAAAIc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YSxX-6NPwYYeeG8pI@P08gAAAIc&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YSxX-6NPwYYeeG8pI@P08gAAAIc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[9] https://www.theregister.com/2021/08/19/intel_architecture_day/
[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YSxX-6NPwYYeeG8pI@P08gAAAIc&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[11] https://www.theregister.com/2021/07/12/linux_5_14_rc1/
[12] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7d2a07b769330c34b4deabeed939325c77a7ec2f
[13] https://whitepapers.theregister.com/
Fancy balls?
I sincerely hope that this is not a hint from Linus that an upcoming version of the Kernel will be sponsored by Manscaped ...
Celebratory Times for Some and a Few, Sack Cloth and Ashes for Others Found Wanting and Worthy
Speaking of Intel, version 5.14 of the kernel adds more support for Chipzilla's Alder Lake platform that puts multiple core types onto a single die and prioritises workloads depending on their needs.
When version 5.14 of the kernel recognises and takes stealthy advantage of Intel platforms that put multiple core needs onto a single die prioritising workloads depending on the type of performance operation, are Spectre and Meltdown type attack vectors more enhanced and hardened/reinforced and re-engineered to react somewhat differently from the expected system programming norms.
I don't imagine Intel thinking that is additional support for their platforms though, whenever it renders their core source foundations compromisable, for it is a catastrophic systemic flaw in their structural base architecture which all but invites remote random renegade rogue access to cores and anonymous third party exploitation of executive functions.
Pop the cork on the next 30
The traditional 30th anniversary gift is a pearl so here's wishing a pearl of a kernal.
I'll try it when the champagne runs out and the hangover cures kick in.