From: Johan Hovold <johan@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
Anton Altaparmakov <anton@tuxera.com>,
Namjae Jeon <linkinjeon@kernel.org>,
ntfs3@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net,
regressions@lists.linux.dev
Subject: Re: [PATCH 1/2] ntfs3: serve as alias for the legacy ntfs driver
Date: Mon, 25 Mar 2024 11:09:28 +0100 [thread overview]
Message-ID: <ZgFNWPCYQC6xYOBX@hovoldconsulting.com> (raw)
In-Reply-To: <20240325-hinkriegen-zuziehen-d7e2c490427a@brauner>
On Mon, Mar 25, 2024 at 09:34:36AM +0100, Christian Brauner wrote:
> Johan Hovold reported that removing the legacy ntfs driver broke boot
> for him since his fstab uses the legacy ntfs driver to access firmware
> from the original Windows partition.
>
> Use ntfs3 as an alias for legacy ntfs if CONFIG_NTFS_FS is selected.
> This is similar to how ext3 is treated.
>
> Fixes: 7ffa8f3d3023 ("fs: Remove NTFS classic")
> Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>
> Cc: Johan Hovold <johan@kernel.org>
> Link: https://lore.kernel.org/r/Zf2zPf5TO5oYt3I3@hovoldconsulting.com
> Signed-off-by: Christian Brauner <brauner@kernel.org>
> ---
> Hey,
>
> This is so far compile tested. It would be great if someone could test
> this. @Johan?
This seems to do the trick. Thanks for the quick fix.
Tested-by: Johan Hovold <johan+linaro@kernel.org>
Do we want to do something about the fact that ntfs mounts may now
become writable as well?
Johan
next prev parent reply other threads:[~2024-03-25 10:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 7:20 [PATCH] fs: Remove NTFS classic Matthew Wilcox (Oracle)
2024-01-15 11:00 ` Anton Altaparmakov
2024-01-15 11:08 ` Enrico Mioso
2024-01-15 11:41 ` Namjae Jeon
2024-01-15 14:49 ` Matthew Wilcox
2024-01-16 9:52 ` [PATCH] " Anton Altaparmakov
2024-01-15 22:20 ` [PATCH] fs: " Dave Chinner
2024-01-16 9:33 ` Christian Brauner
2024-01-16 9:51 ` [PATCH] " Anton Altaparmakov
2024-01-16 11:06 ` Christian Brauner
2024-01-16 11:32 ` Anton Altaparmakov
2024-03-22 16:35 ` [PATCH] fs: " Johan Hovold
2024-03-25 8:28 ` Christian Brauner
2024-03-25 8:34 ` [PATCH 1/2] ntfs3: serve as alias for the legacy ntfs driver Christian Brauner
2024-03-25 10:09 ` Johan Hovold [this message]
2024-03-25 12:01 ` Christian Brauner
2024-03-25 8:34 ` [PATCH 2/2] ntfs3: remove warning Christian Brauner
2024-03-25 10:12 ` Johan Hovold
2024-03-25 12:05 ` Christian Brauner
2024-04-04 8:06 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-11 11:03 ` Konstantin Komarov
2024-04-15 9:54 ` Johan Hovold
2024-04-15 10:20 ` Johan Hovold
2024-04-15 11:32 ` Anton Altaparmakov
2024-04-15 11:42 ` Johan Hovold
2024-04-15 14:15 ` Christian Brauner
2024-04-15 15:23 ` Linus Torvalds
2024-04-15 15:27 ` Matthew Wilcox
2024-04-15 15:47 ` Johan Hovold
2024-04-15 15:51 ` Linus Torvalds
2024-04-15 16:06 ` Johan Hovold
2024-04-16 10:38 ` Christian Brauner
2024-04-16 12:55 ` Johan Hovold
2024-04-17 16:07 ` Konstantin Komarov
2024-04-18 6:36 ` Johan Hovold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZgFNWPCYQC6xYOBX@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=anton@tuxera.com \
--cc=brauner@kernel.org \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=ntfs3@lists.linux.dev \
--cc=regressions@lists.linux.dev \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).