The seventh Linux 7.0 Release Candidate It marks a turning point in the development of the new operating system kernel.What was initially intended to be just another iteration of the 6.x branch with a change in numbering has ended up becoming a particularly busy cycle, with many patches, revisions, and technical debates among the kernel developers.
With Linux 7.0-rc7, the situation has calmed down considerably and everything points to the stable version is very closeLinus Torvalds has put behind him the doubts of previous weeks and now conveys a message of relative calm: the size of the patch is still somewhat larger than usual for this phase, but without anything to raise alarms or require drastic changes of course.
An intense development that gets on track at the end
For much of the cycle, Torvalds had shown a certain discomfort with the volume of changes and the pace of patch integration. However, in this latest announcement, they insist that there have been no "big surprises" and that everything is within reasonable limits for a slightly larger-than-normal RC7. Approximately half of the updated code corresponds to GPU, network, USB and sound drivers, something very common in the kernel, and the other half is divided between kernel corrections, adjustments in the network subsystem, file systems, self-tests, documentation and cryptography.
The general feeling in the community is that the development of Linux 7.0 has been heavier on corrections than in other recent cycles, but without leading to an uncontrollable situation. Torvalds intends to release the stable version soon: if no major setbacks occur, the final release should arrive in the coming days, although the possibility of an eighth Release Candidate remains open should any last-minute problems arise.
Linux 7.0-rc7: Changes focused on stability
This RC7 doesn't introduce any major new features. As is typical in this final phase, the focus is on polish errors and reinforce stabilityThe most significant changes are concentrated in the following areas:
Driver fixes
The largest part of the patch consists of hardware drivers. Several specific groups stand out here:
- GPU Drivers (DRM)Minor fixes have been applied to graphics drivers to prevent crashes, artifacts, or anomalous behavior. These are not new features, but rather improvements to robustness in daily use.
- Network drivers: bugs have been fixed and various drivers optimized, with special attention to the Qualcomm/Atheros Ath11k and Ath12k chips, which are very common in modern laptops and access points as well.
- Other driversThe kernel incorporates adjustments to USB devices, sound, and other specific components, as well as improvements to the input subsystem to support new controllers and laptops.
In the area of ​​input, device identifiers have been added so that the kernel can recognize new ones game controllers within the XPad driver, used for controllers compatible with the Xbox protocol. These include:
- El Razer Wolverine V3 Pro, now supported both in wired mode and via its 2,4 GHz wireless dongle, as its IDs are integrated into the controller.
- The controls BETOP BTP-KP50B and BTP-KP50C, commercially known as Betop Kunpeng 50, which now work correctly with Linux 7.0.
A quirk has also been introduced in the i8042 driver for the TUXEDO InfinityBook Max 16 Gen10 AMDA laptop from the German company TUXEDO Computers, based on a Ryzen AI 9 HX 370 processor, suffered from keyboard issues after sleep and immediate wake-up on subsequent attempts to suspend the system. The new driver adjustment mitigates these problems for more reliable use.
Improvements to the network stack and WiFi
The network subsystem has received a significant set of patches, with a direct impact on the connection quality and performance for multiple environments, including deployments in data centers and home networks.
One particularly noteworthy point is the correction of a performance issue in the WiFi drivers. Ath11k and Ath12kThese drivers, which support 802.11ax devices and other recent Qualcomm chips, suffered from throughput degradation since their integration into the kernel, caused by improper management of aggregation sessions (AMPDU). Under certain traffic conditions, the wrong session would be stopped, drastically reducing the aggregation window size and, consequently, the effective speed.
The patches included in Linux 7.0-rc7 adjust how TID information is passed between internal driver functions, so that The appropriate session should be the one that is modifiedThis same correction pattern applies to both Ath11k (present since 2019) and Ath12k (incorporated in 2022), so users with compatible devices should notice more consistent behavior under load.
In addition, validation improvements have been incorporated into Netfilter to prevent incorrect configurations that could lead to failures or vulnerabilities, as well as other minor patches in wired and wireless network drivers intended to polish small information leaks and bugs detected in recent weeks.
Architectures, file systems, and general kernel
At the architectural level, they are not present new supported processors nor disruptive changes: the work focuses on maintenance tasks to ensure that the various platforms, from ARM servers to x86 PCs, maintain stable behavior.
In file systems like ext4, Btrfs, and XFS, there are no major innovations in this release candidate. The adjustments are focused on fixing specific bugs and cleaning up code to pave the way for future improvements. The lack of significant changes in this area reinforces the idea that the cycle is already in the fine-tuning phase.
Within the general core Bug fixes have been implemented across several internal subsystems, along with minor refactorings and adjustments that do not introduce new features, but do contribute to a more solid foundation for medium-term production deployments.
Security documentation and use of AI in failure reports
One of the peculiarities of Linux 7.0-rc7 is not in the code that directly affects the hardware, but in the security documentationWith the rise of automated analysis tools and language models that scan the kernel's code tree for vulnerabilities, the team has detected a notable increase in the number of bug reports generated by these solutions.
To better manage this flow of reports, the document has been updated. security-bugs.rst With new sections detailing what information is mandatory and what is recommended to include in a security report, the goal is for both human developers and AI tools to be able to send more actionable reports, reducing the need to "chase" authors for proposed patches or key data.
Among the changes, a clearer explanation of how to identify the appropriate contacts for each area of ​​the kernel stands out, so that a fault related to, for example, the network subsystem or a specific driver reaches the correct team without too much back and forth. Although at first glance it may seem like a minor change, this better organization of communication This should translate into a more agile resolution of vulnerabilities, something especially relevant for companies and public administrations that depend on short reaction times.
Impact on performance: the case of PostgreSQL
Alongside these fixes, the Linux 7.0 release cycle has uncovered a striking performance issue that directly affects PostgreSQL databasesAn Amazon/AWS engineer discovered that, with the current development branch of the kernel, PostgreSQL throughput on servers with ARM Graviton4 CPUs was reduced by approximately half compared to previous kernel versions.
After a bisection process, the origin was linked to the changes introduced in Linux 7.0 for simplify planning methods (preemption) In modern architectures, the focus is on full and "lazy" preemption models. These adjustments, intended to streamline scheduler behavior on current CPUs, have nevertheless resulted in certain intensive PostgreSQL workloads spending more time locked in user-space spinlocks.
A patch was proposed to restore PREEMPT_NONE as the default mode in order to reverse the regression, but one of the scheduler's key developers, Peter Zijlstra, has argued that the real solution lies in adapting PostgreSQL to use the extension of Restartable Sequences (RSEQ) with time slice, also introduced in Linux 7.0. This extension allows reducing exposure to problems arising from the preemption of threads that hold locks.
If the kernel change is not ultimately reverted, some PostgreSQL installations may experience performance declines until the database manager itself adopts these new capabilitiesFor organizations deploying PostgreSQL in Linux 7.0 environments, it will be important to closely follow the engine versions and configuration recommendations published by both the PostgreSQL community and the distributions.
Preparations for the stable release of Linux 7.0
With the current fixes and the absence of critical issues, Torvalds anticipates that the stable version of Linux 7.0 It will be released very soon. This kernel is shaping up to be the foundation for future reference distribution releases, including LTS releases that will shape the future of Linux desktops and servers for years to come.
The message to the community remains the same: although the core seems ready, contributors and advanced users are asked to continue. thoroughly testing the rc7 in their test environments. The more varied the configurations and workloads evaluated, from everyday laptops to servers with databases and cloud services, the greater the likelihood of detecting and correcting any residual errors before the final launch.
With Linux 7.0-rc7, the Linux project is approaching a version that, more than for major new features, stands out for consolidating a more stable, better documented and prepared kernel base For a scenario where security, performance on recent hardware, and interaction with artificial intelligence tools are gaining prominence, the combination of fixes to network and GPU drivers, improvements in input device support, adjustments to scheduler behavior, and clearer security documentation points to a release that will serve as a foundation for many of the distributions we will see deployed in the coming months.
