#kernel

91 posts · Last used 13d

Over the past few months, I have found myself under the spotlight on kernel mailing lists. What started as targeted discussions quickly turned into advocating for the kernel community to respect the mostly silent crowd of developers and maintainers who do not want to fully embrace AI usage. It appears this didn't go unnoticed, as shown by Jon Corbet's talk at Kernel Recipes. (1/5) #Linux #kernel #AI
288
8
190
2
[artix/open-rc/iptables] Why did I have to manually load the ip_tables module? I was setting IP iptables like I have done a billion times before, but when trying to /etc/init.d/iptables save, it said that the kernel doesn’t have support for it. Wut? So I load it with modprobe, only to lose it after a reboot, so I shoved it into modules in mkinitcpio.conf, which seems to have helped. What’s going on? Are we forcibly moving on to nftables?
19
8
0
0
[brag + followup] configured and compiled a kernel for the first time ever 🛠️ Following the Arch wiki, I built a custom kernel for the first time ever. It was easier that I thought it’d be, probably because the Arch wiki is so thorough and because I didn’t make that many changes… I just enabled a few FireWire related options as per this guide in order to work on this project (or this). Results/takeaways The OS ran fine with the new kernel 💃 I learned how to manually create GRUB entries 🔧 I learned that I don’t even have to create new GRUB entries, since I can simply point to the new kernel image and initramfs from the bootloader menu 🪛 I learned that my 5800X3D runs well (compiles the new kernel blazingly fast) with all cores set to negative 30 in the UEFI FireWire is dead 💀 Tiny followup on that project That old GPU did something to the UEFI (possibly CMOS?), because even after removing all potentially incompatible hardware and reinstalling my modern GPU, I still got that same error message, saying that the system was forces to boot in CSM mode. Only by resetting the UEFI settings was I able to restore the system to a working state. I admit, I panicked.
60
19
0
0
On my Linux Mint, I see updates about the Linux Kernel Headers 6 (as you can see on screenshot), but currently the machine is running the Kernel 7 (if I follow the command line result). ----- uname -a Linux 7.0.0-28-generic #28~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 1 15:50:57 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ----- Am I wrong, confuse ? (I'm not a kernel expert as you can see 😅 😜 ) Thx for you light 😎 #linuxmint #linux #kernel #question
1
3
1
0
Rust just hit the TIOBE top 10 for the first time — and it's not just hype. The Linux kernel is pushing ~13 CVEs/day, and Greg Kroah-Hartman publicly defended adopting Rust in the kernel specifically for memory safety. Three recent LPEs (CopyFail, Dirty Frag, Fragnesia) were all discovered by AI-assisted tooling within weeks of each other. 50 years of C legacy vs. memory safety in practice. #rustlang #opensource #linux #kernel #infosec
0
0
0
0
Rust entrou no top 10 do TIOBE pela primeira vez — e n\u00e3o \u00e9 s\u00f3 hype. O Linux kernel est\u00e1 emitindo ~13 CVEs/dia, e o Greg Kroah-Hartman defendeu publicamente a ado\u00e7\u00e3o de Rust no kernel justamente por seguran\u00e7a de mem\u00f3ria. Tr\u00eas das \u00faltimas LPEs (CopyFail, Dirty Frag, Fragnesia) foram descobertas por ferramentas AI-assisted em semanas. $ 50 anos de C legado vs. memory safety na pr\u00e1tica. #rustlang #opensource #linux #kernel #infosec
0
0
0
0
🚨 RefluXFS (CVE-2026-64600) has been identified as a notable vulnerability. In the Linux kernel, the following vulnerability has been resolved: xfs: resample the data fork mapping after cycling ILOCK RefluXFS is a local privilege escalation vulnerability in the Linux kernel's XFS filesystem copy-on-write path. It allows local users to overwrite protected files and gain root access. ℹ️ Additional details on ZEN SecDB https://secdb.nttzen.cloud/updates/1d26eb14-ce27-4846-a8ce-bae087fb1e46/refluxfs-vulnerability #infosec #refluxfs #linux #kernel #xfs #lpe #nttdata #zen #secdb
0
0
0
0