Linus Torvalds Criticizes Case‑Insensitive File System Support in Linux

Recently, Linus Torvalds, the creator of Linux, posted a lengthy message on the Linux Kernel Mailing List (LKML) sharply criticizing the case‑insensitive functionality in file systems.

The immediate trigger was a fix patch submitted for the Bcachefs file system. Bcachefs, a copy‑on‑write (COW) file system for Linux, had a patch for case‑folding support submitted two years earlier that never worked; the new patch finally made case‑insensitive directory support functional, and its maintainer Kent Overstreet was blamed for insufficient testing.

Torvalds called the case‑insensitive feature a “huge mistake,” arguing that the problem lies not in inadequate testing but in the decision to implement such functionality at all.

He warned that case‑insensitivity introduces severe security risks, as many user‑space programs rely on filename checks for security‑sensitive patterns, but the file system may ignore non‑printable characters, causing unintended matches; Unicode characters such as “❤” and “❤️” can be treated as identical, leading to misidentification of sensitive files.

Torvalds also expressed anger that developers treat this obvious defect as a “feature,” making user programs vulnerable.

Developers responded with mixed opinions: some supported Torvalds, agreeing that case‑insensitivity poses security hazards and that enforcing case sensitivity is simpler, while others argued that forcing case sensitivity is undesirable, nostalgically recalling older FAT file systems and deeming case‑sensitive designs a regressive step.

The controversy stems from the original design goal of case‑insensitive file systems to accommodate early Windows (FAT, NTFS) and macOS (HFS+) expectations, where File.txt and file.TXT are considered the same file. Linux has traditionally been case‑sensitive, but recent cross‑platform demands have led some Linux file systems to add optional case‑insensitive support, bringing performance overhead, lack of standardization, and security concerns.