#kernel — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #kernel, aggregated by home.social.
-
Linus Torvalds kündigt härteres Vorgehen an
https://linuxnews.de/linus-torvalds-kuendigt-haerteres-vorgehen-an/ #torvalds #ki #kernel #linux #linuxnews -
Linus Torvalds kündigt härteres Vorgehen an
https://linuxnews.de/linus-torvalds-kuendigt-haerteres-vorgehen-an/ #torvalds #ki #kernel #linux #linuxnews -
Linus Torvalds kündigt härteres Vorgehen an
https://linuxnews.de/linus-torvalds-kuendigt-haerteres-vorgehen-an/ #torvalds #ki #kernel #linux #linuxnews -
Linus Torvalds kündigt härteres Vorgehen an
https://linuxnews.de/linus-torvalds-kuendigt-haerteres-vorgehen-an/ #torvalds #ki #kernel #linux #linuxnews -
Linus Torvalds kündigt härteres Vorgehen an
https://linuxnews.de/linus-torvalds-kuendigt-haerteres-vorgehen-an/ #torvalds #ki #kernel #linux #linuxnews -
CVE-2026-28952: Apple macOS 26.5 Kernel Vuln found by Claude
https://support.apple.com/en-us/127115
#HackerNews #CVE202628952 #Apple #macOS #Kernel #Vulnerability #CyberSecurity #Claude
-
CVE-2026-28952: Apple macOS 26.5 Kernel Vuln found by Claude
https://support.apple.com/en-us/127115
#HackerNews #CVE202628952 #Apple #macOS #Kernel #Vulnerability #CyberSecurity #Claude
-
CVE-2026-28952: Apple macOS 26.5 Kernel Vuln found by Claude
https://support.apple.com/en-us/127115
#HackerNews #CVE202628952 #Apple #macOS #Kernel #Vulnerability #CyberSecurity #Claude
-
CVE-2026-28952: Apple macOS 26.5 Kernel Vuln found by Claude
https://support.apple.com/en-us/127115
#HackerNews #CVE202628952 #Apple #macOS #Kernel #Vulnerability #CyberSecurity #Claude
-
CVE-2026-28952: Apple macOS 26.5 Kernel Vuln found by Claude
https://support.apple.com/en-us/127115
#HackerNews #CVE202628952 #Apple #macOS #Kernel #Vulnerability #CyberSecurity #Claude
-
I always remap my
sshddaemon to listen to a non-standard port, to reduce a lot of noise. Which has worked fine for years. But every now and then there are attempts. All the #Linux kernel flaws found lately has made remote login attempts more interesting for attackers. And they scan much more broadly now than just port 22.And that's why my second line of defence is to disallow remote
rootlogin - and also make use of theAllowGroupsfeature insshd_config. Users granted remote access must be member of a specific group. Androotis also excluded from this group.That pays off these days. And this is a nice filter match for #fail2ban and similar tools
I have 293 login attempts on "random users" since May 21. And 259 attempts as
root. -
I always remap my
sshddaemon to listen to a non-standard port, to reduce a lot of noise. Which has worked fine for years. But every now and then there are attempts. All the #Linux kernel flaws found lately has made remote login attempts more interesting for attackers. And they scan much more broadly now than just port 22.And that's why my second line of defence is to disallow remote
rootlogin - and also make use of theAllowGroupsfeature insshd_config. Users granted remote access must be member of a specific group. Androotis also excluded from this group.That pays off these days. And this is a nice filter match for #fail2ban and similar tools
I have 293 login attempts on "random users" since May 21. And 259 attempts as
root. -
I always remap my
sshddaemon to listen to a non-standard port, to reduce a lot of noise. Which has worked fine for years. But every now and then there are attempts. All the #Linux kernel flaws found lately has made remote login attempts more interesting for attackers. And they scan much more broadly now than just port 22.And that's why my second line of defence is to disallow remote
rootlogin - and also make use of theAllowGroupsfeature insshd_config. Users granted remote access must be member of a specific group. Androotis also excluded from this group.That pays off these days. And this is a nice filter match for #fail2ban and similar tools
I have 293 login attempts on "random users" since May 21. And 259 attempts as
root. -
I always remap my
sshddaemon to listen to a non-standard port, to reduce a lot of noise. Which has worked fine for years. But every now and then there are attempts. All the #Linux kernel flaws found lately has made remote login attempts more interesting for attackers. And they scan much more broadly now than just port 22.And that's why my second line of defence is to disallow remote
rootlogin - and also make use of theAllowGroupsfeature insshd_config. Users granted remote access must be member of a specific group. Androotis also excluded from this group.That pays off these days. And this is a nice filter match for #fail2ban and similar tools
I have 293 login attempts on "random users" since May 21. And 259 attempts as
root. -
I always remap my
sshddaemon to listen to a non-standard port, to reduce a lot of noise. Which has worked fine for years. But every now and then there are attempts. All the #Linux kernel flaws found lately has made remote login attempts more interesting for attackers. And they scan much more broadly now than just port 22.And that's why my second line of defence is to disallow remote
rootlogin - and also make use of theAllowGroupsfeature insshd_config. Users granted remote access must be member of a specific group. Androotis also excluded from this group.That pays off these days. And this is a nice filter match for #fail2ban and similar tools
I have 293 login attempts on "random users" since May 21. And 259 attempts as
root. -
Greg KH Calls For More Rust Linux Developers (phoronix.com)
-
[$] Tier-aware memory-controller limits
Joshua Hahn began his session in the memory-management track of the 2026 Linux Storage, Filesystem, Memory Management, and BPF Summit by saying that the memory controller for contr [...]
-
Nuovo allarme sicurezza per Linux: PinTheft può portare a privilegi root su sistemi vulnerabili, con Arch Linux nel mirino. #Linux #ArchLinux #Sicurezza #Kernel #Cybersecurity #OpenSource
-
[$] Dirk and Linus discuss AI and kernel development
Linus Torvalds does not enjoy giving talks, but he does consent to the occasional on-stage conversation with Dirk Hohndel at Linux Foundation events. The pair held the 30th of thei [...]
https://lwn.net/Articles/1073761/ #LWN #Linux #kernel #Git #OSS
-
[$] Dirk and Linus discuss AI and kernel development
Linus Torvalds does not enjoy giving talks, but he does consent to the occasional on-stage conversation with Dirk Hohndel at Linux Foundation events. The pair held the 30th of thei [...]
https://lwn.net/Articles/1073761/ #LWN #Linux #kernel #Git #OSS
-
Linux 7.2 sagt „Auf Wiedersehen“ zu AMDs erstem eigenen x86‑Chip.
- Der Kernel entfernt die Zen 4‑Spezifischen Treiber/Optimierungen.
- Grund: fehlende langfristige Wartbarkeit und schlechte Integration in die aktuelle Kernel‑Architektur.Wer auf AMD‑Zen 4 setzt, muss künftig auf externe Patches oder neuere Kernel‑Versionen ausweichen.
-
Linus Torvalds perde a paciência com correções geradas por IA no kernel
🔗 https://tugatech.com.pt/t84112-linus-torvalds-perde-a-paciencia-com-correcoes-geradas-por-ia-no-kernel -
How Linux system calls actually work?
`bash` can't print to the terminal. `cat` can't read a file. Userspace is sandboxed by hardware - everything goes through the kernel, and that is done through syscalls.
Read more in my article here: https://internals-for-interns.com/posts/linux-kernel-syscalls/
-
#Linux 7.1-rc5 is out:
https://lore.kernel.org/lkml/CAHk-=wjt[email protected]/
""To the surprise of absolutely nobody by now, rc5 is pretty big. Quite a bit bigger than rc5's have traditionally been.
I'm not entirely happy about it - most of this is totally trivial stuff to random drivers, which obviously makes it all less scary, but at the same time I'm really not convinced the churn is worth it at rc5 time. These things are "fixes", sure, but at the same time a lot of them are simply so irrelevant that I think they'd be better off in a linux-next tree and get merged during the merge window.
So I think I'll start being a bit more hardnosed about this kind of unnecessary churn this late in the game. We are supposed to look for *regressions*. Non-critical fixes to long-standing issues are simply not appropriate for this late in the release cycle.
End result: this is too big, and this is the heads-up that I'll be pushing back on pointless pull requests with fixes that just aren't that important. And yes, several of these series were triggered by AI code review.
Because fixes or not - and trivial or not - these kinds of large rc weeks are *not* conducive to long-term stability. Trivial fixes may be trivial, and have a pretty low chance of causing problems, but "low chance" is still not "zero chance".
So people: start looking closer at your pull requests, and ask yourself: "Is this really a regression or serious enough that it shouldn't just go into the development pile?".
Linus""
-
Linux 7.1 RC5 released!
Linux 7.1 RC5 is now live for developers and curious users to try out. All the interesting changes from performance improvements to bug fixes have been integrated to this release candidate.
The official announcement from the kernel mailing list says:
To the surprise of absolutely nobody by now, rc5 is pretty big. Quite a bit bigger than rc5's have traditionally been.
I'm not entirely happy about it - most of this is totally trivial stuff to random drivers, which obviously makes it all less scary, but at the same time I'm really not convinced the churn is worth it at rc5 time. These things are "fixes", sure, but at the same time a lot of them are simply so irrelevant that I think they'd be better off in a linux-next tree and get merged during the merge window.
So I think I'll start being a bit more hardnosed about this kind of unnecessary churn this late in the game. We are supposed to look for *regressions*. Non-critical fixes to long-standing issues are simply not appropriate for this late in the release cycle.
End result: this is too big, and this is the heads-up that I'll be pushing back on pointless pull requests with fixes that just aren't that important. And yes, several of these series were triggered by AI code review.
Because fixes or not - and trivial or not - these kinds of large rc weeks are *not* conducive to long-term stability. Trivial fixes may be trivial, and have a pretty low chance of causing problems, but "low chance" is still not "zero chance".
So people: start looking closer at your pull requests, and ask yourself: "Is this really a regression or serious enough that it shouldn't just go into the development pile?".Why not try out this awesome pre-release of Linux 7.1?
#Computer #Computers #Kernel #Laptop #Laptops #Linux #LinuxKernel #news #Tech #Technology #update -
Linux 7.1 RC5 released!
Linux 7.1 RC5 is now live for developers and curious users to try out. All the interesting changes from performance improvements to bug fixes have been integrated to this release candidate.
The official announcement from the kernel mailing list says:
To the surprise of absolutely nobody by now, rc5 is pretty big. Quite a bit bigger than rc5's have traditionally been.
I'm not entirely happy about it - most of this is totally trivial stuff to random drivers, which obviously makes it all less scary, but at the same time I'm really not convinced the churn is worth it at rc5 time. These things are "fixes", sure, but at the same time a lot of them are simply so irrelevant that I think they'd be better off in a linux-next tree and get merged during the merge window.
So I think I'll start being a bit more hardnosed about this kind of unnecessary churn this late in the game. We are supposed to look for *regressions*. Non-critical fixes to long-standing issues are simply not appropriate for this late in the release cycle.
End result: this is too big, and this is the heads-up that I'll be pushing back on pointless pull requests with fixes that just aren't that important. And yes, several of these series were triggered by AI code review.
Because fixes or not - and trivial or not - these kinds of large rc weeks are *not* conducive to long-term stability. Trivial fixes may be trivial, and have a pretty low chance of causing problems, but "low chance" is still not "zero chance".
So people: start looking closer at your pull requests, and ask yourself: "Is this really a regression or serious enough that it shouldn't just go into the development pile?".Why not try out this awesome pre-release of Linux 7.1?
#Computer #Computers #Kernel #Laptop #Laptops #Linux #LinuxKernel #news #Tech #Technology #update -
Linux 7.1 RC5 released!
Linux 7.1 RC5 is now live for developers and curious users to try out. All the interesting changes from performance improvements to bug fixes have been integrated to this release candidate.
The official announcement from the kernel mailing list says:
To the surprise of absolutely nobody by now, rc5 is pretty big. Quite a bit bigger than rc5's have traditionally been.
I'm not entirely happy about it - most of this is totally trivial stuff to random drivers, which obviously makes it all less scary, but at the same time I'm really not convinced the churn is worth it at rc5 time. These things are "fixes", sure, but at the same time a lot of them are simply so irrelevant that I think they'd be better off in a linux-next tree and get merged during the merge window.
So I think I'll start being a bit more hardnosed about this kind of unnecessary churn this late in the game. We are supposed to look for *regressions*. Non-critical fixes to long-standing issues are simply not appropriate for this late in the release cycle.
End result: this is too big, and this is the heads-up that I'll be pushing back on pointless pull requests with fixes that just aren't that important. And yes, several of these series were triggered by AI code review.
Because fixes or not - and trivial or not - these kinds of large rc weeks are *not* conducive to long-term stability. Trivial fixes may be trivial, and have a pretty low chance of causing problems, but "low chance" is still not "zero chance".
So people: start looking closer at your pull requests, and ask yourself: "Is this really a regression or serious enough that it shouldn't just go into the development pile?".Why not try out this awesome pre-release of Linux 7.1?
#Computer #Computers #Kernel #Laptop #Laptops #Linux #LinuxKernel #news #Tech #Technology #update -
Linux 7.1 RC5 released!
Linux 7.1 RC5 is now live for developers and curious users to try out. All the interesting changes from performance improvements to bug fixes have been integrated to this release candidate.
The official announcement from the kernel mailing list says:
To the surprise of absolutely nobody by now, rc5 is pretty big. Quite a bit bigger than rc5's have traditionally been.
I'm not entirely happy about it - most of this is totally trivial stuff to random drivers, which obviously makes it all less scary, but at the same time I'm really not convinced the churn is worth it at rc5 time. These things are "fixes", sure, but at the same time a lot of them are simply so irrelevant that I think they'd be better off in a linux-next tree and get merged during the merge window.
So I think I'll start being a bit more hardnosed about this kind of unnecessary churn this late in the game. We are supposed to look for *regressions*. Non-critical fixes to long-standing issues are simply not appropriate for this late in the release cycle.
End result: this is too big, and this is the heads-up that I'll be pushing back on pointless pull requests with fixes that just aren't that important. And yes, several of these series were triggered by AI code review.
Because fixes or not - and trivial or not - these kinds of large rc weeks are *not* conducive to long-term stability. Trivial fixes may be trivial, and have a pretty low chance of causing problems, but "low chance" is still not "zero chance".
So people: start looking closer at your pull requests, and ask yourself: "Is this really a regression or serious enough that it shouldn't just go into the development pile?".Why not try out this awesome pre-release of Linux 7.1?
#Computer #Computers #Kernel #Laptop #Laptops #Linux #LinuxKernel #news #Tech #Technology #update -
Linux 7.1 RC5 released!
Linux 7.1 RC5 is now live for developers and curious users to try out. All the interesting changes from performance improvements to bug fixes have been integrated to this release candidate.
The official announcement from the kernel mailing list says:
To the surprise of absolutely nobody by now, rc5 is pretty big. Quite a bit bigger than rc5's have traditionally been.
I'm not entirely happy about it - most of this is totally trivial stuff to random drivers, which obviously makes it all less scary, but at the same time I'm really not convinced the churn is worth it at rc5 time. These things are "fixes", sure, but at the same time a lot of them are simply so irrelevant that I think they'd be better off in a linux-next tree and get merged during the merge window.
So I think I'll start being a bit more hardnosed about this kind of unnecessary churn this late in the game. We are supposed to look for *regressions*. Non-critical fixes to long-standing issues are simply not appropriate for this late in the release cycle.
End result: this is too big, and this is the heads-up that I'll be pushing back on pointless pull requests with fixes that just aren't that important. And yes, several of these series were triggered by AI code review.
Because fixes or not - and trivial or not - these kinds of large rc weeks are *not* conducive to long-term stability. Trivial fixes may be trivial, and have a pretty low chance of causing problems, but "low chance" is still not "zero chance".
So people: start looking closer at your pull requests, and ask yourself: "Is this really a regression or serious enough that it shouldn't just go into the development pile?".Why not try out this awesome pre-release of Linux 7.1?
#Computer #Computers #Kernel #Laptop #Laptops #Linux #LinuxKernel #news #Tech #Technology #update -
Kernel prepatch 7.1-rc5
-
Explorar dev
I have talked before about explorar dev. It's a fancy way to expolore
codein a browser.I use the tried and tested manner of
vim drivers/acpi/acpica/acapps.hgcc source.c
org++ source.c
then read and analyze the code in my favourite Wyze amber terminal 80x25 at 38400bps.Others can't / won't do that. For those who love to burn energy and ram in a massive browser tab, this gem is great to play with.
It is a gem understand me well, just not the feel of a real serial terminal, even one on my IPS LED panels feels more familiar.
Which ever you prefer have fun doing so!
Sources:
man gcc(1)
https://explorar.dev/torvalds/linux
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/rawdiff/?id=v7.1-rc4&id2=v7.0
#programming #Linux #kernel #module #Anubis #protection #gcc #OpenSource #POSIX
-
/* Look ma, no function descriptors! */
https://github.com/torvalds/linux/blob/v7.0/arch/powerpc/kernel/process.c#L1910
-
Linux Mint v3.0 "Cassandra" is tested on VMware Workstation!
#Linux #LinuxMint #Kernel #LinuxKernel #Computers #Laptops #TechNews #TechUpdates
https://officialaptivi.wordpress.com/2026/05/24/linux-mint-v3-0-cassandra-on-vmware-workstation/
-
Researchers disclosed CVE-2026-46333, a Linux kernel flaw present since 2016 that enables local users to access sensitive files and execute commands as root. 🐧
Qualys said Debian, Fedora and Ubuntu default installs are affected, while admins are urged to patch kernels and rotate exposed SSH keys. 🔑🔗 https://thehackernews.com/2026/05/9-year-old-linux-kernel-flaw-enables.html
#TechNews #Linux #Kernel #CVE202646333 #CVE #Cybersecurity #Qualys #Ubuntu #Debian #Fedora #OpenSource #FOSS #Security #Exploit #Infosec #SysAdmin #Privacy #SSH #Admin
-
Researchers disclosed CVE-2026-46333, a Linux kernel flaw present since 2016 that enables local users to access sensitive files and execute commands as root. 🐧
Qualys said Debian, Fedora and Ubuntu default installs are affected, while admins are urged to patch kernels and rotate exposed SSH keys. 🔑🔗 https://thehackernews.com/2026/05/9-year-old-linux-kernel-flaw-enables.html
#TechNews #Linux #Kernel #CVE202646333 #CVE #Cybersecurity #Qualys #Ubuntu #Debian #Fedora #OpenSource #FOSS #Security #Exploit #Infosec #SysAdmin #Privacy #SSH #Admin
-
Researchers disclosed CVE-2026-46333, a Linux kernel flaw present since 2016 that enables local users to access sensitive files and execute commands as root. 🐧
Qualys said Debian, Fedora and Ubuntu default installs are affected, while admins are urged to patch kernels and rotate exposed SSH keys. 🔑🔗 https://thehackernews.com/2026/05/9-year-old-linux-kernel-flaw-enables.html
#TechNews #Linux #Kernel #CVE202646333 #CVE #Cybersecurity #Qualys #Ubuntu #Debian #Fedora #OpenSource #FOSS #Security #Exploit #Infosec #SysAdmin #Privacy #SSH #Admin
