From: liubaolin <liubaolin12138@163.com>
To: DaeMyung Kang <charsyam@gmail.com>, linkinjeon@kernel.org
Cc: hyc.lee@gmail.com, ntfs@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ntfs: compare streams_interface with mounted volume on remount
Date: Mon, 12 Oct 2026 16:25:33 +0800 [thread overview]
Message-ID: <d19c802b-623b-4900-ba09-76302fc7b602@163.com> (raw)
In-Reply-To: <20261012031656.3858771-1-charsyam@gmail.com>
在 2026/10/12 11:16, DaeMyung Kang 写道:
> During reconfiguration, fc->s_fs_info points to a newly allocated
> ntfs_volume. It does not contain the mounted volume's stream setting.
> Consequently, a windows mount rejects a remount with the same
> streams_interface=windows setting, but accepts streams_interface=none
> without changing the active pathname interface. This also breaks an
> ordinary read-only remount when the existing windows setting is passed
> again, for example from fstab.
>
> Compare the requested setting with the mounted volume instead. Use its
> superblock when reporting an unsupported setting change.
>
> Fixes: 2de2cdd9cc08 ("ntfs: add pathname access for named streams")
> Signed-off-by: DaeMyung Kang <charsyam@gmail.com>
> ---
> fs/ntfs/super.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ntfs/super.c b/fs/ntfs/super.c
> index 242fb19ced2b..711e90be9382 100644
> --- a/fs/ntfs/super.c
> +++ b/fs/ntfs/super.c
> @@ -275,8 +275,8 @@ static int ntfs_parse_param(struct fs_context *fc, struct fs_parameter *param)
> result.uint_32 == STREAMS_INTERFACE_WINDOWS;
>
> if (fc->purpose == FS_CONTEXT_FOR_RECONFIGURE &&
> - NVolStreamsWindows(vol) != streams_windows) {
> - ntfs_error(vol->sb,
> + NVolStreamsWindows(NTFS_SB(fc->root->d_sb)) != streams_windows) {
> + ntfs_error(fc->root->d_sb,
> "Cannot change streams_interface on remount.");
> return -EINVAL;
> }
Hi DaeMyung,
The fix looks correct.
However, vol->sb is NULL in the newly allocated volume, so
ntfs_error() only logs the message. Changing the argument to
fc->root->d_sb also invokes the mounted volume’s error-handling policy,
which would trigger a panic on a read-write mount with errors=panic.
This branch only rejects an unsupported option change during
remount; it does not indicate filesystem corruption or an I/O error.
Could we use ntfs_warning(fc->root->d_sb, ...) without triggering
that policy?
Thanks,
Baolin.
next prev parent reply other threads:[~2026-10-12 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 3:16 DaeMyung Kang
2026-10-12 8:25 ` liubaolin [this message]
2026-10-12 9:06 ` CharSyam
2026-10-12 11:27 ` [PATCH v2] " DaeMyung Kang
2026-10-13 6:12 ` liubaolin
2026-10-13 12:38 ` Namjae Jeon
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=d19c802b-623b-4900-ba09-76302fc7b602@163.com \
--to=liubaolin12138@163.com \
--cc=charsyam@gmail.com \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs@lists.linux.dev \
/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
all inboxes | Powered by JetHome®