Linux performance

The Linux 7.2 kernel has officially entered its testing phase following the closure of the merge window and the release of the 7.2-rc1 Git tag. According to Linux creator Linus Torvalds, the kernel now moves into an eight-week stabilization cycle. The release integrates Cache Aware Scheduling, Intel’s USB4STREAM, and the removal of the long-deprecated strncpy API, setting the stage for future enterprise distributions like Fedora 45 and Ubuntu 26.10.

What major features define the Linux 7.2 kernel?

Linux 7.2 introduces a broad array of updates aimed at both performance and hardware compatibility. Development highlights include the implementation of Cache Aware Scheduling to improve CPU efficiency and the integration of the ARCTIC Fan Controller driver. According to reports from Phoronix, the kernel also marks the end of a six-year effort to eliminate the strncpy API, replacing it with safer alternatives. Additionally, the release includes the new AMD ISP4 driver and preliminary support for AMDGPU HDMI 2.1 FRL, signaling an ongoing push toward better display output standards.

How does the current development cycle compare to previous releases?

Linus Torvalds characterized the 7.2-rc1 merge window as “reasonably normal” in his official announcement on the kernel mailing list. While the codebase size remains massive—exceeding 43 million lines—the composition of the changes follows established patterns. Approximately half of the patch volume consists of driver updates. A significant portion of the remaining data is attributed to AMD GPU register definitions, a recurring trend in recent kernel cycles where large header drops account for a substantial percentage of total lines added.

Why is the removal of the strncpy API significant?

The removal of the strncpy API represents a long-term shift toward memory safety within the Linux kernel. Developers have spent six years transitioning away from this interface, which is frequently cited in security audits for its potential to cause buffer overflows or leave strings unterminated. By finalizing this removal in Linux 7.2, the kernel maintainers are reducing the attack surface of the core system, providing a more robust foundation for the security-conscious environments expected in future Ubuntu and Fedora releases.

Did you know?

The Linux kernel is now so large that a single “patch” update often contains more lines of code than entire operating systems from the 1990s. The current 43-million-line count includes everything from core scheduling logic to highly specific hardware drivers for modern GPUs.

Frequently Asked Questions

• When will Linux 7.2 be stable? Following the 7.2-rc1 release, the kernel will undergo approximately eight weeks of testing before the final stable version is released.
• Which Linux distributions will use 7.2? Future releases of Fedora 45 and Ubuntu 26.10 are expected to incorporate this kernel version once it reaches stability.
• What is the most significant change in 7.2? While features like USB4STREAM and Cache Aware Scheduling are notable, the completion of the six-year strncpy API removal is a major milestone for kernel security.

---

Are you planning to test the 7.2-rc1 kernel on your hardware? Join the discussion in the comments below or subscribe to our newsletter for updates on the latest performance benchmarks as they become available.

The KDE Plasma 6.7.2 update, scheduled for release in July, will address critical KWin stability issues and improve performance for Chromium-based applications, according to the official This Week in Plasma blog. Developers are also prioritizing a shift toward a Wayland-only environment for the upcoming Plasma 6.8 release.

How will Plasma 6.7.2 address current stability concerns?

The most immediate fix in the upcoming 6.7.2 release targets a widespread KWin crash occurring in multi-monitor setups that utilize variable refresh rates. KDE developers have confirmed via the official project bug tracker that the fix is already prepared for deployment. Additionally, the update resolves a recurring crash in the KDE Info Center that specifically affected users with certain NVIDIA graphics hardware.

What performance improvements are coming to Chromium apps?

Users of Chromium-based browsers and applications can expect better fullscreen video playback performance in the 6.7.2 update. This optimization follows a series of incremental refinements aimed at smoothing out the desktop experience. Beyond raw performance, the development team is focusing on refining how the desktop interacts with specific hardware drivers to ensure fewer interruptions during daily tasks.

View this post on Instagram about Users of Chromium, Pro Tip

What changes are expected in Plasma 6.8?

Plasma 6.8 is set to deepen the desktop’s reliance on the Wayland display protocol. According to project updates, this version will enable triple buffering by default for NVIDIA GPU users, a change that was previously delayed to ensure stability. Other additions include manual control for wallpaper slideshows, allowing users to trigger changes via the desktop context menu or custom keyboard shortcuts rather than relying on automatic timers.

Why is the move to Wayland-only significant?

The transition to a Wayland-only architecture represents a long-term shift in how KDE manages display rendering. By removing legacy X11 dependencies, developers aim to reduce the maintenance burden and eliminate bugs related to outdated display server protocols. Recent fixes, such as resolving crashes after ejecting audio media in Dolphin or Audex, demonstrate the team’s commitment to stabilizing the core desktop components ahead of this transition.

Frequently Asked Questions

• When will the Plasma 6.7.2 update be available? The update is slated for a July release, following the recent debut of Plasma 6.7.1.
• Does Plasma 6.8 support X11? The project is moving toward a Wayland-only desktop, prioritizing modern protocol support over legacy X11 compatibility.
• Where can I report a KWin crash? You should report issues directly to the KDE Bugzilla, where developers track and verify individual hardware-related crashes.

---

Are you running the latest Plasma release, or are you waiting for the 6.7.2 stability patches? Let us know in the comments below or subscribe to our newsletter for the latest Linux desktop development updates.

Mesa developers have integrated VK_EXT_present_timing support into the Vulkan windowing system integration (WSI) code for X11 and XWayland. This update enables precise frame scheduling and feedback on presentation times for Linux gaming, aiming to reduce stutter and input latency. The feature, developed by Hans-Kristian Arntzen of Valve, will arrive in the Mesa 26.2 release.

How VK_EXT_present_timing Reduces Game Stutter

The VK_EXT_present_timing extension works by allowing applications to communicate their desired presentation time to the display server. According to technical documentation from the Mesa project, this mechanism helps the graphics driver better schedule when a rendered frame appears on the screen. By providing feedback on previous presentation times, the extension allows for improved frame pacing, which is essential for consistent visual smoothness in gaming.

Why X11 and XWayland Support Matters

While Wayland support for present timing has been complete since last year, X11 and XWayland users previously lacked this integration. Hans-Kristian Arntzen of Valve’s Linux team initiated the work to bridge this gap, as noted in the official Mesa merge request. By extending this functionality to X11, the developers ensure that games running via Steam Play—which often rely on X11 or XWayland compatibility layers—can achieve the same frame timing accuracy as native Wayland applications.

Future Trends in Linux Frame Pacing

The integration of this extension signals a broader industry shift toward standardizing display timing across Linux desktop environments. Historically, Linux gaming faced challenges with inconsistent frame delivery compared to Windows due to varying compositor behaviors. By unifying WSI support, the Mesa project is reducing the technical disparity between display protocols. This trend suggests that future Linux gaming updates will focus heavily on “input-to-photon” latency, prioritizing responsiveness for competitive titles.

Frequently Asked Questions

What is the primary benefit of VK_EXT_present_timing?

It helps reduce game stutter and input latency by allowing the application to better control the timing of frame presentation on the display.

When will this feature be available to users?

This support is slated for inclusion in the Mesa 26.2 release, which is expected to arrive in August.

Does this affect Wayland users?

No, Wayland users have already had access to complete present timing support since last year. This update specifically targets the X11 and XWayland back-ends.

---

Are you tracking the latest performance improvements for Linux gaming? Subscribe to our newsletter for weekly updates on Mesa, Steam Play, and open-source graphics driver development.

The Linux kernel has officially removed the strncpy() API in version 7.2, ending a six-year effort to eliminate the function from the codebase. Developers replaced the deprecated string-copying utility with safer, more predictable alternatives to mitigate long-standing security vulnerabilities and performance overheads, according to recent commits in the official Linux kernel source tree.

Why was strncpy removed from the Linux kernel?

Kernel maintainers removed strncpy() because it was a persistent source of memory-related bugs. According to documentation from the Linux kernel maintainers, the function suffered from counter-intuitive semantics regarding NUL-termination. Additionally, the function often caused performance bottlenecks by performing redundant zero-filling on the destination memory. After approximately 362 commits, the kernel no longer relies on this legacy API.

What are the approved replacements for strncpy?

Developers are now required to use specific alternatives that offer better memory safety and explicit behavior. The Phoronix report notes that the kernel now mandates the following functions depending on the use case:

• strscpy(): Used for NUL-terminated destinations where safety is a priority.
• strscpy_pad(): Used when NUL-termination is required alongside zero-padding.
• strtomem_pad(): Reserved for fixed-width fields that do not require NUL-termination.
• memcpy_and_pad(): Used for bounded copies that need explicit padding.
• memcpy(): Reserved strictly for operations where the length of the data is already known.

How does this impact kernel security?

Removing strncpy reduces the “attack surface” of the kernel by eliminating a common point of failure for buffer overflows and incomplete string handling. By forcing developers to use explicit, bounds-checked functions, the kernel team prevents errors where developers might forget to terminate a string. This shift follows a broader industry trend toward memory-safe programming practices, even within low-level C-based environments.

Frequently Asked Questions

Why did it take six years to remove one function?

The Linux kernel is a massive codebase. Replacing a fundamental string function requires careful auditing of thousands of call sites across various CPU architectures to ensure the changes do not introduce regressions or performance issues.

Is memcpy() safer than strncpy()?

memcpy() is not inherently “safer” in terms of logic, but it is more predictable. Unlike strncpy, which has complex and often misunderstood rules about padding and termination, memcpy() performs a straightforward byte copy, making it easier for developers to manage bounds manually.

Will this change affect user-space applications?

No. This change is specific to the Linux kernel API. User-space applications that use the standard C library (glibc) will continue to have access to strncpy, though developers are generally encouraged to use safer alternatives there as well.

---

Are you a kernel developer or a system administrator managing custom modules? Share your experience with the migration process in the comments below, or subscribe to our newsletter for more deep dives into Linux kernel internals.

The Linux 7.2 kernel update introduces native Windows symbolic link support and significant security hardening for its modern NTFS file-system driver. According to developer documentation submitted to the Linux Kernel Mailing List, these updates address long-standing metadata vulnerabilities and improve interoperability for users working across dual-boot environments or shared storage drives.

How does the new NTFS driver improve security?

The latest iteration of the NTFS driver focuses on rigorous validation of on-disk metadata to prevent system crashes and data corruption. As detailed in the official kernel pull request, the update adds strict checks for attributes, index roots, and mapping pairs. These changes are designed to mitigate out-of-bounds access and integer overflow issues that previously plagued the driver. By hardening the code against malformed metadata, the Linux kernel is now less likely to encounter fatal errors when mounting external drives that may have been altered by Windows-side disk utilities.

What are the implications for cross-platform file management?

The inclusion of Windows native symbolic link support marks a shift toward tighter integration between Linux and Windows file systems. Previously, Linux users often struggled with Windows-native links, which are distinct from standard Linux .lnk files. The updated driver now supports both relative and absolute links, as well as junctions, natively. This functionality enables users to bridge the gap between operating systems without needing to reformat drives or rely on third-party user-space tools. By removing unsupported quota code and fixing resource leaks in the fill_super() function, the kernel team has significantly streamlined the driver’s performance footprint.

Future trends in Linux-Windows interoperability

The trajectory of the modern NTFS driver suggests that the kernel community is prioritizing “frictionless” storage support over basic read-only access. Following the “NTFS resurrection” in Linux 7.1, the focus has moved rapidly from simple functionality to enterprise-grade stability. Future kernel updates will likely continue this trend, focusing on deeper support for advanced Windows features like transparent compression or encryption. As Linux gains more widespread use in hybrid cloud and desktop environments, the ability to read and write Windows-formatted drives with native performance and high security will remain a primary development target.

Frequently Asked Questions

Does this update affect my existing WSL symbolic links?

No. The existing behavior for Windows Subsystem for Linux (WSL) symbolic links remains the default. You can choose to use the new native Windows symlink handling via custom mount options if your specific workflow requires it.

Is this driver stable enough for daily use?

Yes. The driver has undergone increased user testing since its introduction in Linux 7.1. The current 7.2 updates specifically target bugs discovered during that testing phase, further stabilizing the driver for general use.

What happens if I try to mount a drive with malformed metadata?

The updated driver includes stricter validation routines that reject or safely handle malformed metadata. This prevents the system from triggering the out-of-bounds accesses or integer overflows that were previously possible.

---

Are you running a dual-boot setup, or do you frequently swap drives between Linux and Windows? Share your experiences with the new NTFS driver in the comments below or subscribe to our newsletter for more kernel development updates.

The Linux 7.2 kernel is set to improve storage performance by optimizing the IOmap framework, which maps file data to physical storage locations. According to reports from Phoronix, a patch from Bytedance engineer Fengnan Chang eliminates redundant memory operations, resulting in a 5% increase in IOPS for EXT4 and XFS file systems when using NVMe SSDs and IO_uring.

How does the IOmap optimization increase storage speed?

The performance boost stems from removing a redundant memset operation within iomap_iter(). As documented in the Linux Kernel Mailing List (LKML) submission, the kernel previously cleared the iomap memory even when the iteration was finished and the data was being discarded. By eliminating this unnecessary write bandwidth, the system reduces overhead in high-IOPS scenarios, specifically 4k random reads using NVMe polling via IO_uring. This streamlined approach allows the CPU to handle more requests per second without requiring hardware upgrades.

What is the significance of FS-VERITY support for XFS?

In addition to performance tuning, the latest VFS pull request includes infrastructure to implement FS-VERITY support for XFS. FS-VERITY is a kernel feature that allows for transparent integrity checking of files using Merkle trees. By adding the necessary VFS hooks, developers are laying the groundwork for XFS to offer file-level authentication, ensuring that data has not been tampered with on disk. This integration mirrors the security evolution seen in other file systems like EXT4 and F2FS, which have already adopted FS-VERITY to protect against silent data corruption and malicious file modification.

How do these changes impact high-performance computing?

The shift toward granular optimizations, such as the two-line code change noted by Fengnan Chang, highlights a trend in kernel development: focusing on micro-optimizations that yield measurable results in data-center environments. While a 5% gain might seem minor in isolation, at the scale of Bytedance’s massive storage arrays, this reduction in memory write bandwidth translates to significant energy savings and improved latency for end-users. These Linux 7.2 updates suggest that the community is prioritizing efficiency in the face of ever-increasing NVMe throughput speeds.

Frequently Asked Questions

What is the primary benefit of the Linux 7.2 IOmap patch?

The patch provides a 5% increase in IOPS for EXT4 and XFS file systems by removing a redundant memory clearing operation during high-speed NVMe polling.

Do I need to update my hardware to see these performance improvements?

No. These are software-level optimizations within the kernel. You will see the benefits once you upgrade to the Linux 7.2 kernel, provided you are using compatible storage technologies like NVMe SSDs.

What does FS-VERITY add to the XFS file system?

It adds support for Merkle tree-based file integrity, allowing the system to verify that file contents have not been altered or corrupted.

---

Are you tracking the performance metrics of your storage stack as you move toward the 7.2 kernel release? Share your findings or questions about IO_uring configurations in the comments below. For more updates on Linux kernel development, explore our latest reports on the 7.2 cycle.

FreeBSD 15.1-RELEASE is now available for download, marking the latest stable iteration of the open-source operating system. Following a two-week delay, the release introduces updated user-space packages, improved NVMe driver support, and expanded hardware compatibility for Intel QuickAssist Technology (QAT) 402xx accelerators. Oracle Cloud Infrastructure (OCI) support has been removed from this version, according to official release documentation from the FreeBSD Project.

What are the key technical updates in FreeBSD 15.1?

The 15.1 release focuses on broadening hardware support and refining kernel-level performance. According to the official release notes, DTrace functionality now extends to 32-bit PowerPC and PowerPC64LE architectures. Developers can now modify CPU schedulers at boot time using the “kern.sched” tunable, a feature aimed at optimizing system performance for specific workloads.

Why was the KDE desktop experience delayed?

Users anticipating a streamlined KDE desktop installation experience will have to wait for the 15.2 release. The FreeBSD development team confirmed that this feature did not meet the stability requirements for the 15.1 launch. This decision follows a pattern of prioritizing core system stability over desktop environment integration in major releases, a strategy that distinguishes FreeBSD’s conservative development cycle from more rapidly evolving Linux distributions.

How does FreeBSD 15.1 compare to previous versions?

The 15.1 release builds upon the foundation of FreeBSD 15.0 by addressing hardware-specific bottlenecks. While 15.0 established the current branch, 15.1 refines the platform through updated OpenZFS file-system support and the implementation of Intel Linear Address Space Separation (LASS) on AMD64 platforms. The removal of OCI support signals a shift in the project’s focus regarding cloud-specific integrations compared to the previous year’s release.

Frequently Asked Questions

• Is FreeBSD 15.1 suitable for production environments? Yes, as a stable release, it is intended for general deployment, though users should audit the release notes for changes in hardware support.
• Where can I download the latest release? Official installation media and checksums are hosted on the FreeBSD Project website.
• Why was OCI support removed? The project has not provided a singular reason, but it reflects ongoing adjustments to the OS’s cloud-native deployment strategy.

---

Are you planning to migrate your existing infrastructure to FreeBSD 15.1? Share your experience with the new kernel tunables in the comments below, or subscribe to our newsletter for deep dives into BSD system administration.

Arch Linux developers have identified and removed malicious code from 1,579 packages within the Arch User Repository (AUR), following a massive security compromise this week. While the repository maintainers state that all known malicious commits have been purged, the incident highlights the ongoing risks inherent in community-maintained software repositories where third-party contributions often bypass rigorous centralized vetting.

How the AUR Security Breach Unfolded

The incident began with an initial report of roughly 400 compromised packages before the scope of the infection rapidly escalated. According to the Arch Linux AUR mailing list, the number of affected packages climbed to 900 within hours, eventually totaling 1,579 identified malicious entries. Developers confirmed that all known malicious commits have been deleted, though they cautioned that the current list of affected packages may not be exhaustive.

Why Community Repositories Face Increased Risks

The AUR operates on a “trust-but-verify” model, which creates a significant attack surface for bad actors. Unlike official distribution repositories that undergo strict package review, the AUR allows users to submit PKGBUILD scripts with minimal oversight. When a maintainer’s account is compromised, the attacker can push malicious updates that automatically reach users who have configured their systems to pull from the repository.

This incident mirrors the XZ Utils supply chain attack reported earlier this year, where attackers spent months gaining trust to inject backdoors into widely used open-source software. Both events demonstrate that the primary vector for modern Linux malware is no longer just individual exploits, but rather the subversion of the software supply chain itself.

What Arch Linux Users Should Do Now

If you have installed or updated software from the AUR recently, security best practices dictate a thorough audit of your system. Even though developers have removed the malicious commits, users who pulled those versions should manually verify their package integrity.

• Review installed packages: Check your recent installation logs for any packages updated during the window of the incident.
• Check AUR comments: The AUR comment section is often the first place community members report suspicious behavior in a specific package.
• Reinstall from source: If you suspect a package may have been compromised, delete the build files and perform a clean install after verifying the upstream source.

Frequently Asked Questions

Are official Arch Linux packages affected?

No. According to the Arch Linux project, the compromise was limited to the Arch User Repository (AUR), which is separate from the official core, extra, and community repositories.

How can I stay safe when using the AUR?

Always inspect the PKGBUILD file before building a package. Avoid installing packages from maintainers with low activity or those that lack a clear, verifiable source code link.

Is the AUR still safe to use?

The AUR remains a powerful tool for Linux enthusiasts, but it requires a higher level of user vigilance. The recent incident serves as a reminder to treat all community-contributed code as potentially untrusted.

Have you checked your system for suspicious packages following this incident? Share your findings or questions in the comments below to help keep the community informed.

Did you know?
The “flatten the pick” patches are not just about raw power; they are about efficiency. By simplifying the run-queue, the Linux kernel can spend less time deciding which task to run next and more time actually processing game frames.

Why Linux USB Support Matters More Than Ever

In the world of open-source development, the Linux kernel is the silent engine powering everything from your smartphone to the largest cloud data centers. While major features grab the headlines, the real work often happens in the maintenance of essential subsystems like USB. As we approach the final stages of the Linux 7.1 cycle, recent updates highlight a critical, ongoing challenge: keeping pace with the quirky, often non-standard hardware manufacturers release into the wild.

Greg Kroah-Hartman’s latest USB pull request serves as a reminder that stability is not accidental—it is the result of thousands of tiny, meticulous fixes. When your external drive fails to mount or your docking station drops connection, it is often these “quirks” that are the unsung heroes keeping your hardware functioning.

The Hidden Battle Against Hardware Incompatibility

The recent patches for Linux 7.1 highlight a recurring theme in hardware engineering: firmware bugs. For instance, the PNY Elite Portable SSD required specific kernel intervention because its Phison-based USB-SATA bridge struggled with standard UAS (USB Attached SCSI) commands. Without these specific “quirks,” the device would simply fail to enumerate or operate at full speed.

This isn’t an isolated incident. The Lenovo ThinkPad USB-C Dock Gen2 also required a patch to disable Link Power Management (LPM) because its hub controllers were suffering from persistent link instability. These real-world examples prove that even top-tier hardware manufacturers often ship products with firmware that doesn’t strictly adhere to USB specifications, forcing the Linux community to act as the ultimate “compatibility layer.”

Future Trends: The RISC-V and USB Evolution

Beyond standard consumer drives and docks, the latest kernel updates also addressed the EIC7700 RISC-V SoC. This is a glimpse into the future. As RISC-V architecture gains traction in embedded systems and edge computing, the Linux kernel must evolve to support these custom SoC designs. We are moving toward a future where “plug and play” will require even more robust driver abstraction layers to handle the diversity of new silicon.

Why Kernel Stability is the Ultimate Competitive Advantage

For enterprise users, this level of attention to detail is why Linux remains the gold standard. While other operating systems might require proprietary driver updates that eventually stop being supported, the Linux kernel approach ensures that once a device is supported, it remains supported for the lifetime of the hardware. This is the definition of evergreen software maintenance.

Frequently Asked Questions

Q: What is a “USB quirk” in the context of the Linux kernel?
A: A quirk is a specific code patch that modifies how the kernel interacts with a particular device to bypass firmware bugs or non-standard behavior that would otherwise cause the device to fail.

Q: Should I update my kernel if my USB devices are working fine?
A: Generally, yes. Kernel updates include security patches and performance improvements that go beyond simple USB fixes, ensuring long-term system health.

Q: How can I report a USB issue I’m having?
A: The best way is to check the Linux Kernel Mailing List (LKML). Ensure you have your hardware ID (via `lsusb`) ready to provide to the developers.

---

What has your experience been with USB hardware on Linux? Have you ever had to troubleshoot a device that just wouldn’t play nice with your kernel? Share your story in the comments below or join our weekly newsletter to keep up with the latest kernel development news.