Search
231 results for “kernellogger”
-
#Linux 7.1-rc3 is out:
https://lore.kernel.org/lkml/CAHk-=wgC[email protected]/
Linus writes: ""[…] this [rc] answers the "is 7.1 continuing the larger size pattern that we saw with 7.0?" question, and the answer is yes: that wasn't a fluke brought on by a .0 release - it simply seems to be the new normal.""
-
#Linux 7.1-rc3 is out:
https://lore.kernel.org/lkml/CAHk-=wgC[email protected]/
Linus writes: ""[…] this [rc] answers the "is 7.1 continuing the larger size pattern that we saw with 7.0?" question, and the answer is yes: that wasn't a fluke brought on by a .0 release - it simply seems to be the new normal.""
-
#Linux 7.1-rc3 is out:
https://lore.kernel.org/lkml/CAHk-=wgC[email protected]/
Linus writes: ""[…] this [rc] answers the "is 7.1 continuing the larger size pattern that we saw with 7.0?" question, and the answer is yes: that wasn't a fluke brought on by a .0 release - it simply seems to be the new normal.""
-
#Linux 7.1-rc3 is out:
https://lore.kernel.org/lkml/CAHk-=wgC[email protected]/
Linus writes: ""[…] this [rc] answers the "is 7.1 continuing the larger size pattern that we saw with 7.0?" question, and the answer is yes: that wasn't a fluke brought on by a .0 release - it simply seems to be the new normal.""
-
Quick reminder in light of the recent #LinuxKernel vulnerabilities:
In case you want to protect yourself against vulnerabilities in #Linux #Kernel modules you don't need, disable module loading completely by running:
echo 1 | sudo tee /proc/sys/kernel/modules_disabled
Of course you want to load all modules you need before running that command, as otherwise you will have to reboot to load them. 😄
More details on this:
* https://dfir.ch/posts/today_i_learned_lkm_kernel.modules_disabled/
* https://linux-audit.com/kernel/increase-kernel-integrity-with-disabled-linux-kernel-modules-loading/
* https://www.heise.de/select/ct/2020/1/1577462303523965 [German] -
Quick reminder in light of the recent #LinuxKernel vulnerabilities:
In case you want to protect yourself against vulnerabilities in #Linux #Kernel modules you don't need, disable module loading completely by running:
echo 1 | sudo tee /proc/sys/kernel/modules_disabled
Of course you want to load all modules you need before running that command, as otherwise you will have to reboot to load them. 😄
More details on this:
* https://dfir.ch/posts/today_i_learned_lkm_kernel.modules_disabled/
* https://linux-audit.com/kernel/increase-kernel-integrity-with-disabled-linux-kernel-modules-loading/
* https://www.heise.de/select/ct/2020/1/1577462303523965 [German] -
Highlights from the main #PowerManagement merge for #Linux 7.0:
""By the number of commits, cpufreq is the leading party (again) and the most visible change there is the removal of the omap-cpufreq driver that has not been used for a long time (good riddance). There are also quite a few changes in the cppc_cpufreq driver, mostly related to fixing its frequency invariance engine in the case […]
Next up is cpuidle and the changes there are dominated by intel_idle driver updates, mostly related to the new command line facility allowing users to adjust the list of C-states used by the driver. […]
The most significant update related to system suspend and hibernation is the one to stop freezing the PM runtime workqueue during system PM transitions which allows some deadlocks to be avoided. […]
[…]and there are assorted cleanups, documentation fixes, and some cpupower utility improvements. […]""
https://git.kernel.org/torvalds/c/9b1b3dcd28c271fc8c4a87e81860f3a34b6d29b7
-
Highlights from the main #PowerManagement merge for #Linux 7.0:
""By the number of commits, cpufreq is the leading party (again) and the most visible change there is the removal of the omap-cpufreq driver that has not been used for a long time (good riddance). There are also quite a few changes in the cppc_cpufreq driver, mostly related to fixing its frequency invariance engine in the case […]
Next up is cpuidle and the changes there are dominated by intel_idle driver updates, mostly related to the new command line facility allowing users to adjust the list of C-states used by the driver. […]
The most significant update related to system suspend and hibernation is the one to stop freezing the PM runtime workqueue during system PM transitions which allows some deadlocks to be avoided. […]
[…]and there are assorted cleanups, documentation fixes, and some cpupower utility improvements. […]""
https://git.kernel.org/torvalds/c/9b1b3dcd28c271fc8c4a87e81860f3a34b6d29b7
-
They joys of bugs in hardware or firmware[1]:
A user reported updating to #Linux #kernel 6.4.y broke #iwlwifi on a Intel 3165 NIC. Bisection identified 5fc3f6c90cc ("r8169: consolidate disabling ASPM before EPHY access") as culprit.
Turns out it was not a faulty bisection, as it seems enabling #ASPM on some #Realtek chips supported by #r8169 can harm other PCI devices. 🥴 🤨
https://bugzilla.kernel.org/show_bug.cgi?id=217635#c27
[1] or maybe it one day turns out that this is caused by a bug somewhere in the #LinuxKernel
-
@kernellogger and use "journalctl -k -b-1" to see the Kernel messages of the previous boot.
Replace "-1" with any of the boot IDs provided by "journalctl --list-boots" (requires the journal to be configured as Storage=persistent in /etc/systemd/journald.conf)
-
#io_uring #bpf filter support was merged for #Linux 7.0 by @axboe
https://git.kernel.org/torvalds/c/591beb0e3a03258ef9c01893a5209845799a7c33 [update] see also: https://lwn.net/Articles/1054225/ and for the liburing side (which has both man pages and an extensive test case that also demonstrate how to use it) https://git.kernel.org/pub/scm/linux/kernel/git/axboe/liburing.git/commit/ [/update]
""This adds support for both cBPF filters for io_uring, as well as task inherited restrictions and filters. […]
seccomp and io_uring don't play along nicely, […] As a result, things like containers and systemd that apply seccomp filters, can't filter io_uring operations.
That leaves them with just one choice if filtering is critical - filter the actual io_uring_setup(2) system call to simply disallow io_uring. That's rather unfortunate, and has limited us because of it.
io_uring already has some filtering support. […] This first adds support for cBPF filters for opcodes, which enables tighter control over what exactly a specific opcode may do. […] These filters are run post the init phase of the request […] On top of that support is added for per-task filters , meaning that any ring created with a task that has a per-task filter will get those filters applied when it's created.[…]""
-
Lai Jiangshan posted a RFC patch-set introducing a new hypervisor called #PVM:
https://lore.kernel.org/lkml/202402261[email protected]/
"'"This RFC series proposes a new virtualization framework built upon the #KVM hypervisor that does not require hardware-assisted virtualization techniques.
So the over-arching goals of PVM are to 1) enable nested virtualization within any IaaS clouds […] 2) avoid costly exits to the host hypervisor […]"'"
Pbonzini already replied: https://lore.kernel.org/lkml/CABgObfaS[email protected]/
-
TIL: The #Linux #kernel has #Klingon language support:
https://docs.kernel.org/admin-guide/unicode.html#klingon-language-support
Qapla'!
-
Wedson Almeida Filho steps down as one of the maintainers of
the #RustForLinux project:'"[…] After almost 4 years, I find myself lacking the energy and enthusiasm I once had to respond to some of the nontechnical nonsense, so it's best to leave it up to those who still have it in them.
To the Rust for Linux team: thank you, you are great. It was a pleasure working with you all; […]"'
-
2/ Side note for users of #Fedora #Linux:
#LinuxKernel 6.12 is now available for all Fedora releases in the "stable" #copr of my #kernel vanilla repositories.
For install instructions, see https://copr.fedorainfracloud.org/coprs/g/kernel-vanilla/stable/ and https://fedoraproject.org/wiki/Kernel_Vanilla_Repositories
In addition to the regular kernel package that copr as of today started shipping a dedicated #realtime kernel which has #PREEMPT_RT enabled. Install it by running:
$ sudo dnf install kernel-rt
-
#Linux v6.12-rc1-rt1 is out:
https://lore.kernel.org/all/2024093015[email protected]/
If you wonder what's still in the RT-Tree now that #PREEMPT_RT support is upstream, checkout https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/log/?h=linux-6.12.y-rt
In short: about 40 patches that among others switch 8250 to nbcon console, add support for ARM and PowerPC, or fix some drivers (like i915).
-
#Linux 6.12-rc1 is out:
https://lore.kernel.org/lkml/CAHk-=wiw[email protected]/
'"Despite conference travel (both for me and several maintainers), things seemed to go mostly fairly normally. There's a couple of notable new features in here: For one thing, #PREEMPT_RT is now mainlined and enabled as a config option (you do need to enable "EXPERT" to get the question). For another, #sched_ext also got merged.
[…]
Let's get the testing and calming down period started, ok?
Linus"'
-
2/ It's done! 🥳
A few minutes ago #PREEMPT_RT (aka: #realtime support) support landed in #Linux mainline, as Linus honored the PR that Tglx handed him yesterday in person (see first toot in thread): https://git.kernel.org/torvalds/c/baeb9a7d8b60b021d907127509c44507539c15e5
Congrats and thx to everyone who was involved in this 20 year long journey!
-
The #Linux 6.12 pull request for #PREEMPT_RT is handed to Linus. Likely the first PR ever submitted in printed form. #kernel #LinuxKernel #Realtime
-
#PREEMPT_RT aka the #realtime support for #LinuxKernel hit #linux-next today! 🥳 👏
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?qt=grep&q=PREEMPT_RT
Still remains to be seen if those changes really makes it upstream during the 6.12 merge window and stick:
* It afaics is still unclear if some #printk prerequisites will be submitted for 6.12: https://lore.kernel.org/all/87ed5za2oj[email protected]/
* Troublemaking changes sometimes are reverted before the final, which in fact happened to some of printk prerequisites a while ago: https://lore.kernel.org/lkml/202206231[email protected]/
-
#Linux #kernel patches to allow enabling #PREEMPT_RT (aka proper #realtime support) for x86, ARM64, and Risc-V were posted for review:
https://lore.kernel.org/lkml/202409061[email protected]/
"The printk bits required for PREEMPT_RT are sitting in linux-next. This was the last known roadblock for PREEMPT_RT. The RT queue has additionally the "atomic console" for the 8250 UART which is not yet in linux-next.[…]"
See also these earlier other related toots:
https://fosstodon.org/@kernellogger/113084762433941141
https://fosstodon.org/@kernellogger/113085326251565367 -
v6 of the patch-set "add threaded printing + the rest" which "provides the remaining pieces of the #printk rework."[1] is now in #Linux-next – but as of now it's not yet clear if this will be merged for #kernel 6.12.
https://lore.kernel.org/all/ZthvGoJE26[email protected]/
[1] e.g. the last big missing piece for #Realtime support through #PREEMPT_RT in the mainline #LinuxKernel. But note, this series does *not* provide an nbcon console driver. That will come in a follow-up series.
-
John posted v4 of the patch-set "threaded console printing as well as some other minor pieces" which "provides the remaining pieces of the #printk rework." -- e.g. the last big missing piece for #Realtime support through #PREEMPT_RT in the mainline #Linux #Kernel. But note, "this series does *not* provide an nbcon console driver. That will come in a follow-up series."
https://lore.kernel.org/all/2024082704[email protected]/
This comes hot on the heels of the "write_atomic() printing" entering -next: https://fosstodon.org/@kernellogger/113003819326920850
-
The improved #printk series "wire up write_atomic() printing" is now in -next again and thus slated for inclusion in #Linux 6.12. This is one of the last important bits for proper #REALTIME support with #PREEMPT_RT in mainline – but not the last, as this series does not include threaded printing or nbcon drivers, as those will come later: https://lore.kernel.org/all/ZsWxpVG8uZ[email protected]/
A earlier version of the patch set was supposed to go into #kernel 6.11, but Linus was unhappy: https://lore.kernel.org/lkml/CAHk-=whU[email protected]/
-
Linus did not pull the latest printk changes for #Linux 6.11, as he did not like the what some of the changes required for proper #Realtime aka #PREEMPT_RT support do:
https://lore.kernel.org/all/CAHk-%3Dwh%[email protected]/
"'
> The messages are flushed at the end of the emergency section to allow storing the full log (backtrace) first.What? No.
One of the historically problematic situations is when a recursive oops or a deadlock occurs *during* the first oops.
[…]
'" #kernel #LinuxKernel -
John posted v3 of the patch-set with the "remaining pieces of the #printk rework" to support threaded console printing, which is last big missing piece missing to support #realtime with the mainline #Linux #kernel through #PREEMPT_RT:
-
The last step in the #Linux #kernel #printk rework saga (the last big pre-requisite before #PREEMPT_RT can be mainlined) is getting closer:
John submitted the printk patch series "add threaded printing + the rest", which '"provides the remaining pieces of the printk rework. All other components are either already mainline or are currently in linux-next. […] Note that this series does *not* provide an nbcon console driver. That will come in a follow-up series."'
-
The content from Netdev 0x16 (held last Oct. 22) is now online.
For a session overview see:
https://netdevconf.info/0x16/accepted-sessions.htmlVideo breakdown:
Day 1: https://bit.ly/netdev-0x16-day-1
Day 2: https://bit.ly/netdev-0x16-day-2
Day 3: https://bit.ly/netdev-0x16-day-3
Day 4: https://bit.ly/netdev-0x16-day-4
Day 5: https://bit.ly/netdev-0x16-day-5 -
Some highlights from various #VFS merges for #Linux 6.17 where @brauner submitted the PR:
https://git.kernel.org/torvalds/c/278c7d9b5e0ca73a75e5151c22fb05c91cb4495f: fallocate() updates bringing support for the BLK_FEAT_WRITE_ZEROES_UNMAP feature and BLK_FLAG_WRITE_ZEROES_UNMAP_DISABLED flag for SCSI, NVMe and device-mapper drivers, and add the FALLOC_FL_WRITE_ZEROES and for ext4 and raw bdev devices; this enables preventing numerous metadata changes and journal I/O, which may lead to significant write amplification and performance degradation in synchronous write mode.
https://git.kernel.org/torvalds/c/57fcb7d930d8f00f383e995aeebdcd2b416a187a: support for the the new file_getattr() and file_setattr() system calls (after lengthy discussions), which allow userspace to set filesystem inode attributes on special files (One of the usage examples is the XFS quota projects.)
https://git.kernel.org/torvalds/c/7879d7aff0ffd969fcb1a59e3f87ebb353e47b7f: ext4 IOCB_DONTCACHE support
https://git.kernel.org/torvalds/c/117eab5c6e31815649d952f6da03f67aa247d29b: An extension to the coredump socket and a proper rework of the coredump code.
-
Interesting detail in the description of the main EFI changes merged for #Linux 6.9[1]:
"'"Avoid creating mappings that are both writable and executable while running in the EFI boot services. This is a prerequisite for getting the x86 #shim loader signed by MicroSoft again, which allows the distros to install on x86 PCs that ship with EFI secure boot enabled."'"
[1] https://git.kernel.org/torvalds/c/70ef654469b371d0a71bcf967fa3dcbca05d4b25