From: Hyunchul Lee <hyc.lee@gmail.com>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: Hyunchul Lee <hyc.lee@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] ntfs: Support Windows native symbolic links
Date: Fri, 12 Jun 2026 16:33:30 +0900 [thread overview]
Message-ID: <20260612-topic-symlink-v1-0-cc1ebf9528e1@gmail.com> (raw)
This patch series adds support for Windows native symbolic links and
introduces mount options to configure how symbolic links are resolved
and created.
Currently, the NTFS driver creates WSL-compatible symbolic links and
has limited support for native Windows symbolic links. This series
addresses these limitations.
1. Following/Resolving Symlinks & Junctions:
- Add support for parsing and following Windows native symbolic links.
- Introduce the "native_symlink=raw|rel" mount option to configure
absolute target resolution.
2. Creating Symlinks:
- Introduce the "symlink=wsl|native" mount option to choose the
creation behavior of symlinks. Under "native", Windows native
symbolic links are created by converting the target path to UTF-16
Windows format.
3. Fixes & Cleanups:
- Fix an issue where the size of symbolic links is reported as 0.
- Clean up target name conversion for WSL symlinks by avoiding
redundant conversion.
4. Documentation:
- Document the newly introduced mount options in ntfs.rst.
Signed-off-by: Hyunchul Lee <hyc.lee@gmail.com>
---
Hyunchul Lee (7):
ntfs: fix incorrect size of symbolic link
ntfs: support following Windows native symlink with relative paths
ntfs: support following Windows native symlink with absolute paths
ntfs: add native_symlink mount option
ntfs: clean up target name conversion for WSL symlinks
ntfs: support creating Windows native symlinks
docs/fs/ntfs: add mount options to support Windows native symbolic links
Documentation/filesystems/ntfs.rst | 13 ++
fs/ntfs/file.c | 24 +-
fs/ntfs/inode.c | 49 ++--
fs/ntfs/inode.h | 2 +
fs/ntfs/layout.h | 19 ++
fs/ntfs/namei.c | 22 +-
fs/ntfs/reparse.c | 461 +++++++++++++++++++++++++++++++++----
fs/ntfs/reparse.h | 6 +-
fs/ntfs/super.c | 38 +++
fs/ntfs/volume.h | 5 +
10 files changed, 563 insertions(+), 76 deletions(-)
---
base-commit: 5aec1efb11ab2a87d1e4be063830268f7980ec4a
change-id: 20260612-topic-symlink-d70873e4721e
Best regards,
--
Thanks,
Hyunchul
next reply other threads:[~2026-06-12 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 7:33 Hyunchul Lee [this message]
2026-06-12 7:33 ` [PATCH 1/7] ntfs: fix incorrect size of symbolic link Hyunchul Lee
2026-06-12 7:33 ` [PATCH 2/7] ntfs: support following Windows native symlink with relative paths Hyunchul Lee
2026-06-12 16:20 ` CharSyam
2026-06-12 7:33 ` [PATCH 3/7] ntfs: support following Windows native symlink with absolute paths Hyunchul Lee
2026-06-12 7:33 ` [PATCH 4/7] ntfs: add native_symlink mount option Hyunchul Lee
2026-06-12 7:33 ` [PATCH 5/7] ntfs: clean up target name conversion for WSL symlinks Hyunchul Lee
2026-06-12 7:33 ` [PATCH 6/7] ntfs: support creating Windows native symlinks Hyunchul Lee
2026-06-12 16:28 ` CharSyam
2026-06-12 7:33 ` [PATCH 7/7] docs/fs/ntfs: add mount options to support Windows native symbolic links Hyunchul Lee
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=20260612-topic-symlink-v1-0-cc1ebf9528e1@gmail.com \
--to=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®