Linus Torvalds announced the release of Linux kernel 6.10 and with it, plenty of new hardware support and improvements to existing hardware. You know the drill.
Announcing the release Torvalds said:
So the final week was perhaps not quote as quiet as the preceding ones, which I don't love - but it also wasn't noisy enough to warrant an extra rc. And much of the noise this last week was bcachefs again (with netfs a close second), so it was all pretty compartmentalized.
In fact, about a third of the patch for the last week was filesystem-related (there were also some btrfs latency fixes and other noise), which is unusual, but none of it looks particularly scary.
Another third was drivers, and the rest is "random".
Anyway, this obviously means that the merge window for 6.11 opens up tomorrow. Let's see how that goes, with much of Europe probably making ready for summer vacation.
Just some cherry-picked items that made it into Linux kernel 6.10 below.
Gaming Related:
- Steam Deck IMU support, plus the kernel now accounts for both versions of the Steam Deck (LCD / OLED).
- NTSYNC driver was merged to hopefully improve Wine / Proton game performance, but not enabled yet.
- Improvements to Xbox Elite 2 controller back paddle buttons over Bluetooth.
- Added support for the Machenike G5 Pro Controller.
- Improved support for some ROG Ally buttons.
- Added support for the ASUS ROG RAIKIRI PRO.
- New support for GameForce Chi retro handheld.
- Improved Aya Neo KUN support.
Other picks:
- Panthor driver for Arm Mali Valhall GPUs landed.
- More work on bringing up support for the upcoming Intel Battlemage.
- A new mseal() syscall for the Linux kernel that "protects the VMAs of a given virtual memory range against modifications", currently Google Chrome plans to hook into it.
- Lots of RISC-V support improvements.
- More WiFi 7 hardware support.
- Lots of new Arm device support across various small boards like the ArmSom Sige7, Forlinx FET3588-C and others.
There's thousands of changes of course that I'm not going to go over, those are just a few bits that jumped out that I thought you might want to know. If I missed anything important and gaming related, be sure to send in a tip.
See more in the full changelog.
Article taken from GamingOnLinux.com.
Quoting: kuhpunktQuoting: ShabbyXQuoting: CedrickThe "nice" era is over
What are you talking about?
Before 6.10 it was 6.9.
69. The sex position.
Ah that kind of nice
Quoting: Vortex_AcheronticQuoting: CedrickThe "nice" era is over
Maybe there will be a 6.66 and later a 6.69 Kernel :>
*Posted from 6.9.9*
Not going to happen until Linus grows some additional fingers and toes...
Quoting: 14And it's immune to CrowdStrike.
only as a racing stripe.
Apperantly Linux servers also encountered this issue, but for linux it was caught by the admins before it could cause an outage.
In conclusion:
Linux is pretty secure, cool and stable, but Linux servers are all those things 10 times more than Linux causes them to be, because they're being managed by Linux users.
Quoting: LoudTechieLooking at that, it would appear that Linux was vulnerable . . . if it was running virtualized Windows with Crowdstrike on it, using VMWare. I'm not sure a vulnerability that only shows up if you're running Windows counts as a Linux vulnerability.Quoting: 14And it's immune to CrowdStrike.
only as a racing stripe.
Apperantly Linux servers also encountered this issue, but for linux it was caught by the admins before it could cause an outage.
In conclusion:
Linux is pretty secure, cool and stable, but Linux servers are all those things 10 times more than Linux causes them to be, because they're being managed by Linux users.
Quoting: Purple Library GuyQuoting: LoudTechieLooking at that, it would appear that Linux was vulnerable . . . if it was running virtualized Windows with Crowdstrike on it, using VMWare. I'm not sure a vulnerability that only shows up if you're running Windows counts as a Linux vulnerability.Quoting: 14And it's immune to CrowdStrike.
only as a racing stripe.
Apperantly Linux servers also encountered this issue, but for linux it was caught by the admins before it could cause an outage.
In conclusion:
Linux is pretty secure, cool and stable, but Linux servers are all those things 10 times more than Linux causes them to be, because they're being managed by Linux users.
Why wouldn't it? Linux should protect itself from whatever garbage may be running in a VM.
Quoting: Purple Library GuyQuoting: LoudTechieLooking at that, it would appear that Linux was vulnerable . . . if it was running virtualized Windows with Crowdstrike on it, using VMWare. I'm not sure a vulnerability that only shows up if you're running Windows counts as a Linux vulnerability.Quoting: 14And it's immune to CrowdStrike.
only as a racing stripe.
Apperantly Linux servers also encountered this issue, but for linux it was caught by the admins before it could cause an outage.
In conclusion:
Linux is pretty secure, cool and stable, but Linux servers are all those things 10 times more than Linux causes them to be, because they're being managed by Linux users.
No the linux was virtualized and crashed.
All his "debian vms" crashed.
Meaning all his vms running debian.
There exists a native version of crowdstrike falcon for linux.
What you describe would have been much, much worse.
That would've been a vm escape exploit, a privilege escalation exploit and a kernel panic(bsod for linux) in one.
Edit:
Translated in less-nerdish the last part would bring it from a stability issue to a critical security exploit and a stability issue.
Last edited by LoudTechie on 23 July 2024 at 10:12 am UTC
Patreon
PayPal
See more from me