Technology

Linux 7.1 drops NTFS limits and kills 486

Linux 7.1 arrives with a new in-kernel NTFS driver aimed at making Microsoft file handling feel “first-class,” enables Intel’s FRED by default, and adds Intel LASS-based hardening and crypto improvements. It also accelerates legacy cleanup by ending Intel 486

On his way to Mumbai for the Open Source Summit India, Linus Torvalds announced the latest Linux kernel: 7.1.

The release is a point version on paper, but it lands with a sense of finality. For everyday users. the biggest visible shift is that Linux 7.1 introduces a brand-new in-kernel implementation of Microsoft’s New Technology File System (NTFS). For older systems, the message is much harsher: this kernel continues ripping out support for Intel’s 486-class processors.

Linux 7.1 arrives only months after Linux 7.0 debuted with major networking and filesystem changes, and 7.1 keeps tightening the hardware focus while improving performance and security.

The most immediate change for many people comes from NTFS. Linux users who deal with Microsoft file systems—whether they’re moving data between Windows and Linux. using external drives. or dual-booting—have often had to rely on third-party workarounds. Linux 7.1 replaces both the older NTFS-3G FUSE driver in many setups and the Paragon-contributed NTFS3 kernel driver. which had a bumpy history including data-corruption reports.

Torvalds described the new driver as an “NTFS resurrection.” Under the hood. the new code is built on Linux’s contemporary filesystem infrastructure. using iomap and folios instead of older buffer_head-centric paths. The goal is not just better speed in some cases. but robust read-write support. better error handling. and more predictable behavior when there’s heavy parallel I/O.

The performance picture is nuanced. Linux 7.1’s NTFS developer, Namjae Jeon, said the new driver shows only modest single-threaded write gains. But when multiple threads hit the same NTFS volume. the improvements jump sharply: multi-threaded writes can be 35–110% faster than earlier drivers. Even mounting is faster, with mounting a 4TB NTFS volume reported to be roughly four times faster.

That’s the kind of difference that changes the day-to-day feeling of a system for people who shuffle files back and forth. NTFS stops being something you “make work” and starts behaving more like a first-class citizen on Linux desktops and laptops.

On the CPU side. Linux 7.1 flips the switch on Intel’s Flexible Return and Event Delivery (FRED). enabling it by default on supported Intel platforms. FRED is a hardware mechanism for handling entries and exits in privileged modes—interrupts. exceptions. and system calls—aimed at simplifying control-flow transitions and reducing reliance on legacy entry stacks that have grown increasingly complex and insecure.

By moving to FRED, the kernel gets a cleaner separation between user and kernel control flows. The release notes expect some overhead to shrink in high-frequency event handling, and the direction is also described as improving the security story around those transitions.

For now, the benefits will show up mostly on recent Intel client and server hardware. But the point is to be ready for more vendors choosing similar mechanisms as time goes on.

Security is also a central theme. Linux 7.1 adds support for Intel’s Linear Address Space Separation (LASS). LASS constrains how code accesses different regions of the linear address space. which makes certain classes of memory-corruption and control-flow attacks harder to exploit by enforcing stronger separation between code and data regions. It works alongside FRED. and together they’re framed as an architectural shift toward hardening the boundary between userland and kernel. as well as between different types of in-kernel objects.

The crypto subsystem gets a rework too, enabling more optimizations by default. That’s expected to pay off wherever encryption and hashing are hot paths—TLS stacks, VPNs, encrypted filesystems, and distributed storage.

And while Intel’s updates are front-and-center, the kernel also prepares for what’s next from AMD. Linux 7.1 includes further enablement for AMD’s upcoming Zen 6 processors. with new IDs. errata workarounds. and tuning hooks landing in the release. aimed at getting the kernel ready for the next wave of EPYC and Ryzen parts when they hit the market.

But the other half of the story is where the release feels most uncompromising. Linux 7.1 continues the process of aggressively removing support for Intel’s 486-class processors and other early x86 variants. Kernel maintainers have telegraphed the move for some time. and mainstream distributions had long since moved their baselines to at least i586 or x86-64. No major Linux distro currently supports 486 processors, as far as the article notes.

The cleanup goes beyond CPUs. The codebase sheds over 140,000 lines of legacy code, including obsolete network and PCMCIA drivers, and it removes Baikal CPU support. The rationale is two-fold: reducing the attack surface exposed by ancient. barely tested code paths. and easing long-term maintenance by freeing developers from preserving behaviors for hardware that has vanished from production.

For retro-computing enthusiasts, the path doesn’t disappear entirely—older kernels can still be run. But the line between “supported” and “museum piece” is getting sharper.

Taken together. Linux 7.1 is doing two things at once: bringing NTFS into the modern kernel with a new in-kernel driver. while also pruning the parts of the codebase that belong to a different era. There’s a practical human payoff in the NTFS changes for people who regularly move files across Windows and Linux. And there’s a sharper boundary being drawn underneath—between hardware the kernel is eager to run well and hardware it’s no longer willing to carry.

For everyday users, that likely means smoother, safer interaction with NTFS-formatted drives. For operators and OEMs. the story shifts toward security posture. platform support. and being ready for the next wave of Intel and AMD silicon—because the kernel is preparing for what’s current. and refusing to keep paying the cost of what isn’t.

Linux 7.1 NTFS driver FRED LASS kernel security Linux NTFS-3G NTFS3 Open Source Summit India Intel 486 support legacy cleanup crypto subsystem iomap folios Intel Flexible Return and Event Delivery

4 Comments

  1. So wait, Linux can just read NTFS better now? Finally. I swear every other update is like “trust us” then it breaks something in a week.

  2. Intel FRED and LASS sounds like made up marketing words. Also if it’s “in-kernel” does that mean it’s gonna mine bitcoins too? Like why else would they harden crypto.

  3. My cousin said NTFS support means you don’t need Windows anymore, but then they said it still won’t open everything. And now 486 is being removed like what, they’re mad at old CPUs? I just want it to not mess up my dual boot, that’s all.

Leave a Reply

Your email address will not be published. Required fields are marked *

Are you human? Please solve:Captcha