Search
320 results for “kernellogger”
-
From the main #ntfs3 merge for #Linux 6.17[1]:
"Added:
- sanity check for file name
- mark live inode as bad and avoid any operationsFixed:
- handling of symlinks created in windows
- creation of symlinks for relative pathChanged:
- cancel setting inode as bad after removing name fails
- revert 'replace inode_trylock with inode_lock'"[1] https://git.kernel.org/torvalds/c/a11b4fa602ed3b744aa075f34bee82c12aa3553a
-
From the main #ntfs3 merge for #Linux 6.17[1]:
"Added:
- sanity check for file name
- mark live inode as bad and avoid any operationsFixed:
- handling of symlinks created in windows
- creation of symlinks for relative pathChanged:
- cancel setting inode as bad after removing name fails
- revert 'replace inode_trylock with inode_lock'"[1] https://git.kernel.org/torvalds/c/a11b4fa602ed3b744aa075f34bee82c12aa3553a
-
From the main #ntfs3 merge for #Linux 6.17[1]:
"Added:
- sanity check for file name
- mark live inode as bad and avoid any operationsFixed:
- handling of symlinks created in windows
- creation of symlinks for relative pathChanged:
- cancel setting inode as bad after removing name fails
- revert 'replace inode_trylock with inode_lock'"[1] https://git.kernel.org/torvalds/c/a11b4fa602ed3b744aa075f34bee82c12aa3553a
-
2/ And to quote one bit from @corbet's[1] great #OSSNA25 talk:
""[…] there will be no core development conferences around #Linux and other things in the United States in the foreseeable future. […] this is a real problem […]""
Yes, this is not a formal announcement[2] – but it bears some weight, as Jonathan is well connected and among others sits in the Linux Foundation's Technical Advisory Board (TAB).
[1] https://www.youtube.com/watch?v=hNLBGiwfBSI&t=949s (for context starts a bit earlier; the quoted bit comes about a minute later)
[2] and kinda obvious for some of you
-
ICYMI: the recording of @corbet's recent #OSSNA25 talk "Three Decades in Kernelland" recently became available:
https://www.youtube.com/watch?v=hNLBGiwfBSI
From the abstract[1]: The #Linux #kernel project has been going for well over 30 years. From its beginnings on floppy diskettes and beige boxes through to its current home in pockets and unseen data centers, the kernel project has been a constant exercise in rapid development and adaptation. I have been present for almost all of the kernel project's history as an observer, contributor, maintainer, and more; all that experience will be boiled down into a fast-moving tour of how the #LinuxKernel got to where it is, what makes it successful, and what may be coming next.
[1] https://ossna2025.sched.com/event/1zfit/three-decades-in-kernelland-jonathan-corbet-lwnnet
-
Using machine learning to optimize/fine-tune the #Linux #kernel at runtime to the needs of the workload – this is something I guess we'll see way more often in the future.
The recent #ossna25 talk "Improve Load Balancing With Machine Learning Techniques Based on the #sched_ext Framework" from Ching-Chun ("Jim") Huang gives a glimpse into such a future.
@lwn write-up: https://lwn.net/Articles/1027096/
Recording: https://www.youtube.com/watch?v=5VXemIXAOrI
-
A document describes techniques that are useful for debugging suspend and resume issues with modern #AMD processors was merged for #Linux 6.16: https://git.kernel.org/torvalds/c/cafb22242bfb7fad10fde6f9b99853fc924e691a
Rendered version: https://origin.kernel.org/doc/html/next/arch/x86/amd-debugging.html
-
Support task local hash maps[1], FUTEX2_NUMA[2], and FUTEX2_MPOL[3] was merged for #Linux 6.16:
https://git.kernel.org/torvalds/c/b3570b00dc3062c5a5e8d9602b923618d679636a
See also: https://lore.kernel.org/all/2025041616[email protected]/
[1] https://git.kernel.org/torvalds/c/80367ad01d93ac781b0e1df246edaf006928002f
[2] https://git.kernel.org/torvalds/c/cec199c5e39bde7191a08087cc3d002ccfab31ff
[3] https://git.kernel.org/torvalds/c/c042c505210dc3453f378df432c10fff3d471bc5
-
A option to optimize the code for the local CPU was merged for #Linux 6.16:
https://git.kernel.org/torvalds/c/ea1dcca1de129dfdf145338a868648bc0e24717c
To quote: '"Add a 'native' option that allows users to build an optimized kernel for their local machine (i.e. the machine which is used to build the kernel) by passing '-march=native' to CFLAGS.
The idea comes from Linus' reply to Arnd's initial proposal:
https://lore.kernel.org/all/CAHk-=wji1[email protected]/
Here are some numbers comparing 'generic' to 'native' on a Skylake dual-core laptop (generic --> native) […]
There is little difference both in terms of size and of performance, however
the native build comes out on top ever so slightly [3 % in some cases]."'Note, the author tried in on a different machine later, and there it made no real difference:
-
Highlights from the main #erofs merge for #Linux 6.16 (https://git.kernel.org/torvalds/c/79b98edf918e8146047e08817e2a42937428be02):
* a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.
* Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.
-
Highlights from the main #erofs merge for #Linux 6.16 (https://git.kernel.org/torvalds/c/79b98edf918e8146047e08817e2a42937428be02):
* a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.
* Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.
-
Highlights from the main #erofs merge for #Linux 6.16 (https://git.kernel.org/torvalds/c/79b98edf918e8146047e08817e2a42937428be02):
* a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.
* Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.
-
Highlights from the main #erofs merge for #Linux 6.16 (https://git.kernel.org/torvalds/c/79b98edf918e8146047e08817e2a42937428be02):
* a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.
* Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.
-
Highlights from the main #erofs merge for #Linux 6.16 (https://git.kernel.org/torvalds/c/79b98edf918e8146047e08817e2a42937428be02):
* a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.
* Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.
-
Highlights from the main #XFS merge for #Linux 6.16 (https://git.kernel.org/torvalds/c/f83fcb87f824b0bfbf1200590cc80f05e66488a7):
- Atomic writes for XFS
- Remove experimental warnings for pNFS, scrub and parent pointers
-
Highlights from the main #bcachefs merge for #Linux 6.16: https://git.kernel.org/torvalds/c/522544fc71c27b4b432386c7919f71ecc79a3bfb
- Incompatible features may now be enabled at runtime, via "opts/version_upgrade" in sysfs.
- Various changes to support deployable disk images
- Major error message improvements for btree node reads, data reads, and elsewhere.
- New option, 'rebalance_on_ac_only'.
- Repair/self healing:
- We can now kick off recovery passes and run them in the background if we detect errors.
- Performance:
- Faster snapshot deletion
- Faster device removal
- We're now coalescing redundant accounting updates prior to transaction commit, taking some pressure off the journal.
- Stack usage improvements: All allocator state has been moved off the stack -
"some performance improvements and one minor mount option update" are among the main #Btrfs changes merged for #Linux 6.16:
https://git.kernel.org/torvalds/c/5e82ed5ca4b510e0ff53af1e12e94e6aa1fe5a93
A few highlights:
Performance:
- extent buffer conversion to xarray gains throughput and runtime improvements on metadata heavy operations doing writeback (sample test shows +50% throughput, -33% runtime)
- extent io tree cleanups lead to performance improvements by avoiding unnecessary searches or repeated searches
- more efficient extent unpinning when committing transaction (estimated run time improvement 3-5%)
User visible changes:
- remove standalone mount option 'nologreplay', deprecated in 5.9, replacement is 'rescue=nologreplay'
- in scrub, update reporting, add back device stats message after detected errors (accidentally removed during recent refactoring)
Core:
- convert extent buffer radix tree to xarray
- continued preparations for large folios -
'"[…] The default dialect in #GCC 15 is still -std=gnu++17. You can use the -std=c++23 or -std=gnu++23 command-line options to enable C++23 features, and similarly for C++26 and others. […] C++26 features in #GCC15 include pack indexing, attributes for structured bindings, enhanced support for functions whose definition consists of =delete, and more. […] A number of defect reports were resolved in GCC 15. A few examples follow. […] C++11 attributes in C++98 […]"'
https://developers.redhat.com/articles/2025/04/24/new-c-features-gcc-15
-
"[…] Let's take a look at 6 improvements to look forward to in the upcoming #GCC 15.
1. Prettier execution paths
2. A new look for C++ template errors
3. Machine-readable diagnostics
4. An easier transition to C23
5. A revamped color scheme
6. libgdiagnostics
We're still fixing bugs, but we hope that GCC 15 will be ready to officially release (as 15.1) sometime later this month. […]"'
https://developers.redhat.com/articles/2025/04/10/6-usability-improvements-gcc-15 – by David Malcolm #gcc15
-
#WattWise: A lightweight CLI tool for monitoring power usage from smart plugs in real-time, either directly or through Home Assistant.
https://www.naveen.ing/cli-for-smartplugs/
See also: https://github.com/naveenkul/WattWise
Naveen Kulandaivelu writes:
'"WattWise started as a simple utility [for] monitoring a power-hungry workstation from the terminal I already have open. The addition of automatic power management during peak ToU hours has already saved me from manually adjusting system performance throughout the day."'
-
Ohh, there was another discussion on #LKML about "modern #Linux distros should be more careful mounting untrusted storage devices, as they might contain maliciously corrupted filesystems that can cause the #kernel to fail"
Good entry point to the discussion: https://lore.kernel.org/all/Z8948cR5ak[email protected]/t/#u
"[…] We've tried for years to get userspace to adopt a more security-aware model for untrusted devices, but have made pretty much no progress. […]"
-
Have you heard the claim "Changing 30 lines of code in the #Linux #kernel could cut energy use at some data centers by up to 30 percent" that made the news two or three weeks ago?
Did you wonder if it is really that simple as it sounds in many stories? Then you want to read the following article from @LWN. It describes things in a more nuanced and technical way, as yes, it is not that simple:
https://lwn.net/Articles/1008399/ #LinuxKernel #networking #powerefficiency
-
Have you heard the claim "Changing 30 lines of code in the #Linux #kernel could cut energy use at some data centers by up to 30 percent" that made the news two or three weeks ago?
Did you wonder if it is really that simple as it sounds in many stories? Then you want to read the following article from @LWN. It describes things in a more nuanced and technical way, as yes, it is not that simple:
https://lwn.net/Articles/1008399/ #LinuxKernel #networking #powerefficiency
-
Have you heard the claim "Changing 30 lines of code in the #Linux #kernel could cut energy use at some data centers by up to 30 percent" that made the news two or three weeks ago?
Did you wonder if it is really that simple as it sounds in many stories? Then you want to read the following article from @LWN. It describes things in a more nuanced and technical way, as yes, it is not that simple:
https://lwn.net/Articles/1008399/ #LinuxKernel #networking #powerefficiency
-
Have you heard the claim "Changing 30 lines of code in the #Linux #kernel could cut energy use at some data centers by up to 30 percent" that made the news two or three weeks ago?
Did you wonder if it is really that simple as it sounds in many stories? Then you want to read the following article from @LWN. It describes things in a more nuanced and technical way, as yes, it is not that simple:
https://lwn.net/Articles/1008399/ #LinuxKernel #networking #powerefficiency
-
Have you heard the claim "Changing 30 lines of code in the #Linux #kernel could cut energy use at some data centers by up to 30 percent" that made the news two or three weeks ago?
Did you wonder if it is really that simple as it sounds in many stories? Then you want to read the following article from @LWN. It describes things in a more nuanced and technical way, as yes, it is not that simple:
https://lwn.net/Articles/1008399/ #LinuxKernel #networking #powerefficiency
-
GNU #Binutils 2.44 is out:
https://lists.gnu.org/archive/html/info-gnu/2025-02/msg00001.html
Some highlights:
* Assembler:
- Support for new architecture extensions for AArch64, Risc-V and x86.* Linker:
- This now supports mixed LTO and non-LTO object files in relocatable output.
- The ELF forms of the linker support a --image-base=<ADDR> option for compatibility with LLD.[…] does not contain the sources for the gold linker […] now deprecated and will eventually be removed unless volunteers step forward […]
-
2/ #RPMFusion wants to ship an *add-on* pkg for #Fedora with vulkan drivers that support hw video acceleration for patent encumbered codecs.
-
Wanna know what's in store for Linux 6.13, which is expected to be released on January 19 or 26?
Then check out these articles from #LWNnet now freely available:
* The beginning of the 6.13 merge window – https://lwn.net/Articles/998623/
* The rest of the 6.13 merge window – https://lwn.net/Articles/998990/
-
And with "reiserfs: The last commit", #reiserfs is now gone from #Linux for 6.13:
https://git.kernel.org/torvalds/c/fb6f20ecb121cef4d7946f834a6ee867c4e21b4a
63 files changed, 12 insertions, 32804 deletions
Bye bye! 👋