[PATCH 09/14] Documentation: filesystems: Fix stale reference to device-mapper docs
From: Bagas Sanjaya <hidden>
Date: 2025-08-29 07:55:46
Also in:
bpf, damon, dri-devel, linux-devicetree, linux-doc, linux-mm, linux-pm, linux-sound, lkml, netdev, workflows
Subsystem:
documentation, fsverity: read-only file-based authenticity protection, the rest, ubi file system (ubifs) · Maintainers:
Jonathan Corbet, Eric Biggers, Theodore Y. Ts'o, Linus Torvalds, Richard Weinberger
Commit 6cf2a73cb2bc42 ("docs: device-mapper: move it to the admin-guide")
moves device mapper docs to Documentation/admin-guide, but left
references (which happen to be external ones) behind, hence 404 when
clicking them.
Fix the references while also converting them to internal ones.
Signed-off-by: Bagas Sanjaya <redacted>
---
Documentation/filesystems/fsverity.rst | 11 +++++------
Documentation/filesystems/ubifs-authentication.rst | 4 ++--
2 files changed, 7 insertions(+), 8 deletions(-)
diff --git a/Documentation/filesystems/fsverity.rst b/Documentation/filesystems/fsverity.rst
index 412cf11e329852..54378a3926de7b 100644
--- a/Documentation/filesystems/fsverity.rst
+++ b/Documentation/filesystems/fsverity.rst@@ -15,12 +15,11 @@ of read-only files. Currently, it is supported by the ext4, f2fs, and btrfs filesystems. Like fscrypt, not too much filesystem-specific code is needed to support fs-verity. -fs-verity is similar to `dm-verity -<https://www.kernel.org/doc/Documentation/admin-guide/device-mapper/verity.rst>`_ -but works on files rather than block devices. On regular files on -filesystems supporting fs-verity, userspace can execute an ioctl that -causes the filesystem to build a Merkle tree for the file and persist -it to a filesystem-specific location associated with the file. +fs-verity is similar to :doc:`dm-verity +</admin-guide/device-mapper/verity>` but works on files rather than block +devices. On regular files on filesystems supporting fs-verity, userspace can +execute an ioctl that causes the filesystem to build a Merkle tree for the file +and persist it to a filesystem-specific location associated with the file. After this, the file is made readonly, and all reads from the file are automatically verified against the file's Merkle tree. Reads of any
diff --git a/Documentation/filesystems/ubifs-authentication.rst b/Documentation/filesystems/ubifs-authentication.rst
index 106bb9c056f611..9fcad59820915d 100644
--- a/Documentation/filesystems/ubifs-authentication.rst
+++ b/Documentation/filesystems/ubifs-authentication.rst@@ -439,9 +439,9 @@ References [DMC-CBC-ATTACK] https://www.jakoblell.com/blog/2013/12/22/practical-malleability-attack-against-cbc-encrypted-luks-partitions/ -[DM-INTEGRITY] https://www.kernel.org/doc/Documentation/device-mapper/dm-integrity.rst +[DM-INTEGRITY] Documentation/admin-guide/device-mapper/dm-integrity.rst -[DM-VERITY] https://www.kernel.org/doc/Documentation/device-mapper/verity.rst +[DM-VERITY] Documentation/admin-guide/device-mapper/verity.rst [FSCRYPT-POLICY2] https://lore.kernel.org/r/20171023214058.128121-1-ebiggers3@gmail.com/
--
An old man doll... just what I always wanted! - Clara