On Mon, Apr 15, 2024 at 08:51:13AM -0700, Linus Torvalds wrote:
> On Mon, 15 Apr 2024 at 08:47, Johan Hovold <jo...@ke...> wrote:
> >
> > I think the "ntfs" alias must always be mounted read-only because you
> > can currently have an fstab entry which does not specify "ro" and this
> > mount would suddenly become writeable when updating to 6.9 (possibly by
> > a non-privileged user, etc).
>
> Well, it would be fairly easy to do particularly if we just do it for
> the old legacy case.
>
> Of course, even the legacy case had that CONFIG_NTFS_RW option, so
> people who depended on _that_ would want to be able to remount...
Ah, right, I forgot about CONFIG_NTFS_RW as I've never enabled it.
Judging from the now removed Kconfig entry perhaps not that many people
did:
The only supported operation is overwriting existing files,
without changing the file length. No file or directory
creation, deletion or renaming is possible.
but I guess it still makes my argument above mostly moot.
At least if we disable write support in ntfs3 by default for now...
Johan
|