From: Namjae Jeon <linkinjeon@kernel.org>
To: hyc.lee@gmail.com
Cc: ntfs@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, sebastian.n.feld@gmail.com,
cedric.blancher@gmail.com, Lionelcons1972@gmail.com,
Namjae Jeon <linkinjeon@kernel.org>
Subject: [PATCH v2 4/4] ntfs: document named streams
Date: Wed, 7 Oct 2026 07:40:24 +0900 [thread overview]
Message-ID: <20261006224024.14535-5-linkinjeon@kernel.org> (raw)
In-Reply-To: <20261006224024.14535-1-linkinjeon@kernel.org>
Document the streams_interface=windows mount option and named-stream
pathname semantics, including supported forms and stream lifetime.
Describe the named-stream ioctl operations, request structure, and name
encoding.
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
---
Documentation/filesystems/ntfs.rst | 34 ++++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
diff --git a/Documentation/filesystems/ntfs.rst b/Documentation/filesystems/ntfs.rst
index 4bfa392daec6..ec329bb142a0 100644
--- a/Documentation/filesystems/ntfs.rst
+++ b/Documentation/filesystems/ntfs.rst
@@ -169,4 +169,38 @@ symlink=wsl|native Configure how symbolic links are created. Under
Linux) compatible symlinks are created. Under
"native", Windows native symbolic links are
created.
+
+streams_interface= Select the named-stream pathname interface:
+ "none" (default) treats ':' as an ordinary filename
+ character, while "windows" interprets the final
+ component of a path such as "file:stream" as a named
+ $DATA stream. In "windows" mode, filenames containing
+ ':' are hidden from directory listings and cannot be
+ addressed through the pathname interface. Only the
+ file:stream form is recognized. Typed forms such
+ as file::$DATA and file:stream:$DATA are not
+ supported. The ioctl interface is available in both
+ modes. The base file or directory must already exist
+ before a pathname stream can be created. Creating
+ file:stream does not create file. Removing a stream
+ while it is open fails with -EBUSY. Removing the base
+ file while a stream is open detaches the stream from
+ the namespace; NTFS has no orphan-stream list, so a
+ crash can leave that stream's data unreachable on
+ disk.
======================= ====================================================
+
+Named-stream ioctls
+===================
+
+The named-stream ioctl interface is available regardless of
+streams_interface. Open the base regular file or directory and use
+NTFS_IOC_STREAM_READ and NTFS_IOC_STREAM_WRITE with a
+struct ntfs_stream request. The request contains the stream name,
+byte offset, and transfer length. Write requests create the stream when it
+does not exist. A failed write can leave a newly created empty stream; use
+NTFS_IOC_STREAM_REMOVE to remove it. This ioctl removes streams, and
+NTFS_IOC_LIST_STREAMS enumerates streams. Stream names are encoded with
+the mounted NLS by default. Set NTFS_STREAM_FL_UTF16 to pass or receive
+raw UTF-16LE names. These ioctls transfer stream data directly and do not
+return a separate stream file descriptor.
--
2.25.1
prev parent reply other threads:[~2026-10-06 22:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 22:40 [PATCH v2 0/4] ntfs: add named data stream support Namjae Jeon
2026-10-06 22:40 ` [PATCH v2 1/4] ntfs: add named stream ioctls support Namjae Jeon
2026-10-07 2:07 ` CharSyam
2026-10-07 2:24 ` Namjae Jeon
2026-10-06 22:40 ` [PATCH v2 2/4] ntfs: add pathname access for named streams Namjae Jeon
2026-10-07 3:38 ` CharSyam
2026-10-07 5:05 ` Namjae Jeon
2026-10-06 22:40 ` [PATCH v2 3/4] MAINTAINERS: ntfs: add UAPI header Namjae Jeon
2026-10-06 22:40 ` Namjae Jeon [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=20261006224024.14535-5-linkinjeon@kernel.org \
--to=linkinjeon@kernel.org \
--cc=Lionelcons1972@gmail.com \
--cc=cedric.blancher@gmail.com \
--cc=hyc.lee@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs@lists.linux.dev \
--cc=sebastian.n.feld@gmail.com \
/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®