linux-kernel - Re: [PATCH v3 12/14] Revert: ntfs3: serve as alias for the legacy ntfs driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAKYAXd979DqSVOFzMA8H_LSs+xjd67cVofFbKn98WupKW-K5jg@mail.gmail.com>
Date: Tue, 30 Dec 2025 09:12:51 +0900
From: Namjae Jeon <linkinjeon@...nel.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: viro@...iv.linux.org.uk, brauner@...nel.org, hch@...radead.org, hch@....de, 
	tytso@....edu, jack@...e.cz, djwong@...nel.org, josef@...icpanda.com, 
	sandeen@...deen.net, rgoldwyn@...e.com, xiang@...nel.org, dsterba@...e.com, 
	pali@...nel.org, ebiggers@...nel.org, neil@...wn.name, amir73il@...il.com, 
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, 
	iamjoonsoo.kim@....com, cheol.lee@....com, jay.sim@....com, gunho.lee@....com
Subject: Re: [PATCH v3 12/14] Revert: ntfs3: serve as alias for the legacy
 ntfs driver

On Tue, Dec 30, 2025 at 9:03 AM Namjae Jeon <linkinjeon@...nel.org> wrote:
>
> On Tue, Dec 30, 2025 at 1:41 AM Matthew Wilcox <willy@...radead.org> wrote:
> >
> > On Mon, Dec 29, 2025 at 07:59:30PM +0900, Namjae Jeon wrote:
> > > ntfs filesystem has been remade and is returning as a new implementation.
> > > ntfs3 no longer needs to be an alias for ntfs.
> >
> > I don't think this is right.  If one has selected ntfs3 as built-in
> > then one still needs pieces of this to handle classic ntfs
> > configurations, no?
> ntfsplus has been renamed to ntfs as you requested. Wouldn't it be
> confusing for users if they probably expect the new read-write
> implementation to be used, but instead the read-only path from ntfs3
> could be triggered ?
And, if ntfs3 is built-in or already insmoded, they can not be used
simultaneously because ntfs.ko cannot be insmoded.