The Ubuntu Kernel Team issued a statement this morning to proactively warn Ubuntu Linux users on Ubuntu 26.04 and Ubuntu 24.04 LTS HWE users that the next kernel point release will contain a performance regression for AMD GPUs in compute-heavy workloads with up to a 42x performance hit. The positive news is that due to this being an upstream regression in a Linux 7.0 point release, upstream stakeholders and other Linux distributions that more quickly shipped the problematic code already have a fix coming down the pipe...
Now in the upstream linux-firmware.git centralized repository is the firmware binary needed for enabling the Imagination Tech PowerVR BXM-4-64 Rogue GPU found with the Alibaba T-Head TH1520 SoC...
As a follow-up to the article over ROCm 7.14 being tagged, AMD has formally announced the availability of ROCm 7.14 and it's their new production release rather than being a tech preview...
Caerus is a new GTK4 graphical front end for Void Linux’s XBPS, offering package search, bulk actions, transaction previews, and system maintenance tools.
AMD's software team appears to be busy getting ready for next week's Advancing AI event happening next week in San Francisco. In addition to the release today of the Lemonade 11.0 local AI server, TheRock 7.14 was also tagged as the modern build system for ROCm working on the latest tech preview releases of this open-source AMD GPU compute stack...
Mozilla is changing Firefox’s release schedule from September, with new stable versions planned every two weeks instead of once a month. The company says the new release cadence is designed to make releases more predictable and allow improvements to reach users more often. But in a message to developers, Mozilla described the changes as an experiment and said it will review the impact before deciding whether to continue. Firefox 154, due for release on 18 August, will be the final stable version released under the current schedule. Firefox 155 is then planned for 1 September, after which new stable releases […]
The removal of GPL code from FreeBSD 16’s base system isn’t just housekeeping — it reflects a BSD vision of “software freedom” that differs from FSF, Gnu, and Linux. The post FreeBSD 16 Cleans House: No GPL Left in the Base System appeared first on FOSS Force.
It should come as no surprise that a gathering of filesystem developers would discuss filesystem testing; it has been a mainstay of the Linux Storage, Filesystem, Memory Management, and BPF Summit over the years and the 2026 summit was no exception. Ted Ts'o led the discussion this time; he had a few different topics to raise, including his perception of increasing regressions for ext4 in the stable kernels and what can be done to help reduce them. As with other similar sessions at the summit over the years, there is a lot of interest in collaborating on test inputs and outputs, but finding a way to centralize that information has so far eluded the filesystem community.
The SUSE Security Team Blog has a post with an analysis of seunshare, which is used by SELinux to confine untrusted programs. During a review of version 3.10 of the program, the team identified two local Denial-of-Service (DoS) vectors. Since seunshare is supposed to run on SELinux-enabled systems, it is important to understand what kind of privilege escalation can be achieved when vulnerabilities are exploited in a setuid-root binary like this. Many SELinux-enabled systems, such as Fedora and openSUSE, ship with the "targeted" SELinux policy by default. This policy is focused on confining well-known system services, but assigns an unconfined SELinux context to interactive users by default to achieve a balance between security and usability. There is currently no domain transition from the unconfined domain to the more restricted seunshare_t defined in the SELinux policy for seunshare. This means the execution of seunshare continues in the unconfined domain. Thus in the context of atta
Ahead of the AMD Advancing AI event next week, today AMD released Lemonade 11.0 as the latest feature release of their local AI server supporting AMD Ryzen CPUs, AMD Radeon GPUs, and AMD Ryzen AI NPU acceleration...
Processes that use io_uring tend to keep a lot of balls in the air; being able to have many operations underway at any given time is part of the point of that API in the first place. The io_uring subsystem must, as a result, keep track of a lot of tasks that have to be performed at the right time. In current kernels, io_uring uses a standard kernel linked-list primitive to track those work items. As of the 7.2 kernel release, though, io_uring will, instead, use a new lockless, multi-producer, single-consumer (MPSC) queue, resulting in some notable performance gains. Lockless algorithms tend to be tricky, but the one used here is relatively approachable and shows how these algorithms can work.
Linux News