From: DaeMyung Kang <charsyam@gmail.com>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: Hyunchul Lee <hyc.lee@gmail.com>,
Baolin Liu <liubaolin12138@163.com>,
ntfs@lists.linux.dev, linux-kernel@vger.kernel.org,
DaeMyung Kang <charsyam@gmail.com>
Subject: [PATCH v2] ntfs: compare streams_interface with mounted volume on remount
Date: Mon, 12 Oct 2026 20:27:55 +0900 [thread overview]
Message-ID: <20261012112755.1353990-1-charsyam@gmail.com> (raw)
In-Reply-To: <20261012031656.3858771-1-charsyam@gmail.com>
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. Report
an unsupported change with ntfs_warning() so it does not invoke the
mounted filesystem's error-handling policy.
Fixes: 2de2cdd9cc08 ("ntfs: add pathname access for named streams")
Signed-off-by: DaeMyung Kang <charsyam@gmail.com>
---
Changes in v2:
- Use ntfs_warning() so a rejected option change does not invoke the
mounted volume's error policy, as Baolin suggested.
- Explain in the commit message why logging must not invoke the mounted
filesystem's error policy.
Link to v1: https://lore.kernel.org/r/20261012031656.3858771-1-charsyam@gmail.com
fs/ntfs/super.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/ntfs/super.c b/fs/ntfs/super.c
index 242fb19ced2b..ed9f29b16c7c 100644
--- a/fs/ntfs/super.c
+++ b/fs/ntfs/super.c
@@ -275,9 +275,9 @@ 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,
- "Cannot change streams_interface on remount.");
+ NVolStreamsWindows(NTFS_SB(fc->root->d_sb)) != streams_windows) {
+ ntfs_warning(fc->root->d_sb,
+ "Cannot change streams_interface on remount.");
return -EINVAL;
}
if (streams_windows)
--
2.43.0
prev parent reply other threads:[~2026-10-12 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 3:16 [PATCH] " DaeMyung Kang
2026-10-12 8:25 ` liubaolin
2026-10-12 9:06 ` CharSyam
2026-10-12 11:27 ` DaeMyung Kang [this message]
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=20261012112755.1353990-1-charsyam@gmail.com \
--to=charsyam@gmail.com \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liubaolin12138@163.com \
--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®