On Mon, Apr 15, 2024 at 08:23:46AM -0700, Linus Torvalds wrote: > On Mon, 15 Apr 2024 at 07:16, Christian Brauner <brauner@xxxxxxxxxx> wrote: > > > > (1) Since the ntfs3 driver is supposed to serve as a drop-in replacement > > for the legacy ntfs driver we should to it the same way we did it > > for ext3 and ext4 where ext4 registers itself also for the ext3 > > driver. In other words, we would register ntfs3 as ntfs3 filesystem > > type and as legacy ntfs filesystem type. > > I think that if just registering it under the same name solves the > immediate issue, that's the one we should just go for. I agree. > > To make it fully compatible > > we also need to make sure it's persistently mounted read-only. > > My reaction to that is "only if it turns out we really need to". Unfortunately, we do. It seems that ntfs3 has some bugs, and (according to Anton, the ntfs-classic maintainer) it's actually corrupting perfectly good filesystems. I'd expected that this kind of bug would have been shaken out by now (it's been in the kernel for over two and a half years!) but it seems like people just haven't been using it.
