File Systems on KnightLi Blog

Linux 7.0 and 7.1 NTFS Driver Changes Explained

Sat, 02 May 2026 10:46:20 +0800

After Linux 7.0, Linux 7.1 entered the next feature merge window. One notable change is a new NTFS kernel driver.

“New” does not mean Linux is supporting NTFS for the first time, nor does it mean ntfs3 is being replaced. More precisely, Linux 7.1 adds a new optional in-kernel NTFS read-write driver. It is based on the old in-kernel ntfs driver, modernized and extended with more complete write support.

Quick Take

Linux now has three main NTFS paths:

Option	Location	Read-write support	Best fit
`ntfs-3g`	User-space FUSE	Read-write	Stability first; long-time distro default
`ntfs3`	Kernel-space	Read-write	More direct kernel integration and performance
New `ntfs`	Kernel-space	Read-write	Optional implementation added in Linux 7.1

This is not a forced migration. It simply adds another option. Most users can keep following their distribution defaults for now.

How 7.0 and 7.1 Relate

Linux 7.0 only marks the move into the 7.x kernel series. It does not mean NTFS support was suddenly rewritten in 7.0. The NTFS-related change appears in the Linux 7.1 feature cycle.

NTFS remains important for Linux desktop users because dual-boot systems, external drives, USB drives, and Windows data disks often use it. The hard part is writes: if a file-system driver has a bug, user data can be affected directly. That is why NTFS driver changes are treated carefully.

`ntfs-3g`, `ntfs3`, and the New `ntfs`

ntfs-3g is a user-space FUSE driver. It has long handled NTFS read-write support on Linux. It may not always be the fastest option, but it is mature, compatible, and well documented.

ntfs3 is the in-kernel NTFS driver contributed by Paragon Software and already merged into Linux. It has a shorter path, integrates more directly with VFS, and can offer better performance. But file-system drivers require strong maintenance discipline, and ntfs3 has seen discussion around maintenance pace and code quality after merging.

The new Linux 7.1 ntfs driver is maintained by Namjae Jeon. It is not written from scratch; it modernizes the old kernel ntfs driver, adds write support, and coexists with ntfs3 as another optional implementation.

In short:

ntfs-3g: conservative, mature, user-space.
ntfs3: existing in-kernel mainline option.
New ntfs: new in-kernel option in 7.1, still worth watching.

Which One to Use

There is no need to switch immediately. A conservative order is:

Keep using the distribution default for important data, usually ntfs-3g or a tested ntfs3.
Try ntfs3 when performance matters.
Test the new ntfs driver on temporary, test, or recoverable data first.
Back up important NTFS partitions before writing.

To mount with ntfs3 manually:

`1`	`sudo mount -t ntfs3 /dev/sdX1 /mnt/ntfs`

For temporary read-only access:

`1`	`sudo mount -o ro /dev/sdX1 /mnt/ntfs`

To check which driver is being used:

1
2

findmnt -T /mnt/ntfs
mount | grep ntfs

Dual-Boot Notes

If an NTFS partition comes from a Windows system disk, make sure Windows is fully shut down before writing to it. Fast Startup and hibernation can leave the NTFS volume in an unfinished state, and Linux writes may then cause consistency problems.

Check these first:

Disable Windows Fast Startup.
Make sure the partition is not hibernated.
Confirm BitLocker or other encryption is not blocking access.
Safely eject external drives from Windows.

These rules apply whether you use ntfs-3g, ntfs3, or the new ntfs driver.

Why Multiple NTFS Drivers Exist

Multiple implementations for the same file system are not unusual in Linux. Old, new, vendor, and community implementations can coexist until maintenance status and real-world feedback make the preferred path clear.

NTFS is especially suited to a conservative approach:

User data risk is high.
Compatibility cases are complex.
Implementations differ in performance and stability tradeoffs.
Distributions need time to validate defaults.

So the new Linux 7.1 ntfs driver does not immediately obsolete ntfs-3g or ntfs3. It gives the kernel community another maintainable option.

Summary

The new Linux 7.1 ntfs driver is an optional in-kernel NTFS read-write implementation. It coexists with ntfs-3g and ntfs3; it does not directly replace either.

Regular users can keep using distribution defaults. Users who want to test performance or kernel file-system changes can watch ntfs3 and the new ntfs, but important data should be backed up before switching drivers.

Linux Kernel 7.0 Feature Update Overview

Fri, 01 May 2026 14:46:07 +0800

Linux kernel version numbers have never followed semantic versioning. A major version bump is more about the project’s rolling maintenance rhythm. In the release message, Linus Torvalds also described 7.0 as a normal release: the final week mostly contained small fixes across networking, architecture code, tools, selftests, and drivers.

What is really worth watching is the set of incremental changes itself. Linux 7.0 covers file systems, memory management, hardware support, security isolation, Rust support, and driver cleanup.

File Systems: XFS, EXT4, and NTFS3 All Changed

File systems are one of the most visible update areas in Linux 7.0.

XFS introduces self-healing-related capabilities. Together with a new generic file-system error reporting mechanism, file systems can report metadata corruption and I/O errors to user space in a more unified way. With suitable system service support, XFS can automatically handle some repair flows while the file system remains mounted. This does not mean every disk corruption problem can be fixed painlessly, but for servers and long-running systems, the detection and repair path is more complete.

EXT4 continues to improve concurrent direct I/O write performance. If a machine often runs backups, builds, downloads, databases, or log tasks that write to disk at the same time, these optimizations should make concurrent write paths steadier. It is not the kind of change every desktop user will immediately notice, but it matters for heavy I/O scenarios.

NTFS3 also receives a larger driver update, including delayed allocation, iomap-based file operations, and better readahead for large directory scans. If you often access Windows partitions or external NTFS disks from Linux, these updates are worth noting.

In addition, exFAT improves multi-cluster sequential reads, which can make sequential reading faster on some small-cluster devices.

Memory and Swap: Better Behavior Under Memory Pressure

Linux 7.0 continues the cleanup work around the swap subsystem from recent releases. One focus is improving the path for reading pages back from swap, especially when multiple processes share the same swapped-out pages. Throughput should be better in those cases.

For desktop users, this may not feel like the system suddenly becoming faster. But on memory-constrained systems, dense container hosts, Redis-like services with persistence enabled, or zram setups backed by disk, these changes can reduce jitter under memory pressure.

zram paths also receive optimizations. Previously, in some cases, the kernel needed to decompress zram pages before writing them to a backing device. The new path can write compressed data directly, reducing unnecessary processing.

CPU and Performance: Intel TSX auto, Faster Threads and File Operations

Linux 7.0 adjusts the default policy for Intel TSX. Because of past security issues, TSX was disabled by default on many processors. The kernel now uses a more precise auto policy: affected CPUs continue to keep it disabled, while unaffected or suitable CPUs can enable it automatically.

This can help some multithreaded workloads, especially applications that rely on transactional synchronization extensions. It is not a universal acceleration switch; the actual benefit still depends on the CPU model and whether the application uses the feature.

Linux 7.0 also includes optimizations for PID allocation, thread creation and destruction, and file open/close paths. These optimizations usually do not become headline features on their own, but they accumulate into small gains in system responsiveness and high-concurrency services.

Hardware Support: New Platform Enablement and Existing Device Improvements

Linux 7.0 continues a large amount of hardware enablement work. These updates usually fall into two groups: preparation for platforms that are not yet widely available, and improvements for devices already in users’ hands.

For new platforms, Linux 7.0 includes more preparation for Intel Nova Lake, Intel Crescent Island, new AMD graphics IP, and AMD Zen 6. These changes may not matter to ordinary users right away, but they determine whether new hardware can receive mainline kernel support more quickly after release.

On ARM64 and single-board computers, H.264/H.265 hardware video decoding for Rockchip RK3588/RK3576 enters the mainline support scope. This means devices such as Orange Pi 5 and Radxa ROCK 5 no longer need to rely entirely on vendor BSP kernels for hardware decoding.

There are also many detailed updates for laptops and peripherals:

ASUS WMI improves backlight, keyboard lighting, and fan hotkey support for ROG and TUF models.
HP WMI adds manual fan control for some Victus models and fixes audio indicator lights.
Lenovo WMI exposes more HWMON monitoring information for Legion devices.
The Intel Xe graphics driver exposes more temperature sensors.
Intel Arc B-series discrete GPUs can enter deeper PCIe power-saving states.
Rock Band 4 Bluetooth guitars and the Logitech K980 Bluetooth keyboard get better kernel support.

Each of these changes is small on its own, but for laptop, gaming device, development board, and peripheral users, more complete mainline support makes future distribution maintenance easier.

Security and Isolation: io_uring Can Use BPF Filtering

Linux 7.0 adds BPF filtering support to io_uring. This matters for containers, sandboxes, and environments with high security requirements.

In the past, some administrators disabled io_uring entirely to reduce attack surface. With BPF filtering, they can now restrict allowed operations more precisely instead of choosing only between fully enabled and fully disabled.

This does not make io_uring risks disappear automatically, but it gives system administrators and runtime frameworks a more controllable isolation tool.

Rust Support Is No Longer Just an Experimental Label

In Linux 7.0, the status of Rust for Linux becomes more stable. This does not mean the kernel will be rewritten in Rust at large scale, nor does it mean C is being replaced.

More precisely, the infrastructure for Rust in the kernel has entered a more formal stage. Future drivers, subsystems, or some security-sensitive code can choose Rust where it fits. This is a gradual path: stabilize the interfaces, build system, documentation, and maintenance process first, then let actual code grow over time.

Removing Old Functionality: laptop_mode Is Gone

Linux 7.0 removes laptop_mode. This was a long-standing power-saving feature mainly designed for the hard-disk laptop era, reducing disk wakeups to save power.

Modern laptops are mostly SSD-based, and the kernel’s memory reclaim, block device, and file-system paths have changed a lot. Keeping this old mechanism increases maintenance cost, and its test coverage was not ideal. Removing it reduces the impact of old code on modern paths.

Linux 7.0 adds several new HID keycodes for contextual AI interaction, such as acting on selected content, inserting context-generated content, and starting contextual queries.

This is not AI functionality built into the kernel. It is more like reserving input event definitions for future laptop keyboards and peripherals, so desktop environments, applications, or vendor tools can recognize those keys. What they actually do still depends on distribution, desktop environment, and application-level integration.

Should You Upgrade Immediately?

If you use a rolling distribution, Linux 7.0 will likely arrive naturally through system updates. If you use a newer distribution such as Ubuntu 26.04 LTS, 7.0 may also appear as the default or primary kernel version.

But if your machine is a production server, NAS, virtualization host, or depends on closed-source drivers and proprietary kernel modules, do not upgrade manually just because the version number became 7.0. A safer approach is to:

wait for the distribution to provide official kernel packages;
check compatibility for graphics cards, network cards, ZFS, VirtualBox, VMware, and DKMS modules;
test first on a test machine or snapshot environment;
watch the 7.0.x point releases.

As of the kernel.org v7.x directory, 7.0.1, 7.0.2, and 7.0.3 have already been released. If you plan to build or test manually, prefer the latest stable 7.0.x release instead of focusing only on the initial 7.0 tarball.

Summary

Linux Kernel 7.0 is not a release that rewrites everything just because the major version changed. It is closer to a broad regular kernel update: file systems are more reliable, swap and I/O paths continue to improve, new hardware support moves forward, and Rust, io_uring isolation, and HID input definitions fill in infrastructure needed for long-term evolution.

For ordinary desktop users, the most practical changes may come from hardware support, graphics drivers, power saving, and file-system repair. For servers and developers, XFS error reporting, self-healing, io_uring BPF filtering, swap optimization, and new platform support are more worth watching.

References:

File Systems on KnightLi Blog

Linux 7.0 and 7.1 NTFS Driver Changes Explained

Quick Take

How 7.0 and 7.1 Relate

ntfs-3g, ntfs3, and the New ntfs

Which One to Use

Dual-Boot Notes

Why Multiple NTFS Drivers Exist

Summary

Linux Kernel 7.0 Feature Update Overview

File Systems: XFS, EXT4, and NTFS3 All Changed

Memory and Swap: Better Behavior Under Memory Pressure

CPU and Performance: Intel TSX auto, Faster Threads and File Operations

Hardware Support: New Platform Enablement and Existing Device Improvements

Security and Isolation: io_uring Can Use BPF Filtering

Rust Support Is No Longer Just an Experimental Label

Removing Old Functionality: laptop_mode Is Gone

AI-Related Keys: Preparing for a New Generation of Keyboard Interaction

Should You Upgrade Immediately?

Summary

`ntfs-3g`, `ntfs3`, and the New `ntfs`