Skip to contentSkip to conversation

docs: Remove remainders of reiserfs

PATCH In review David Sterba 6 participants 6 messages Aug 13, 2025 – Aug 18, 2025

Subsystems (6)
lore
Share & tools
lore

David Sterba

author maintainer
#0 lore raw

PATCH 1/1 docs: Remove remainders of reiserfs

Reiserfs has been removed in 6.13, there are still some mentions in the documentation about it and the tools. Remove those that don't seem relevant anymore but keep references to reiserfs' r5 hash used by some code.

There's one change in a script scripts/selinux/install_policy.sh but it does not seem to be relevant either.

---
 Documentation/admin-guide/ext4.rst                 |  2 +-
 Documentation/admin-guide/laptops/laptop-mode.rst  |  8 ++++----
 .../arch/powerpc/eeh-pci-error-recovery.rst        |  1 -
 .../translations/it_IT/process/changes.rst         | 14 --------------
 fs/btrfs/tree-log.c                                |  2 +-
 scripts/selinux/install_policy.sh                  |  2 +-
 6 files changed, 7 insertions(+), 22 deletions(-)
Documentation/admin-guide/ext4.rst +1 -1
index b857eb6ca1b620..ac0c709ea9e7c1 100644
@@ -398,7 +398,7 @@ There are 3 different data modes:
 * writeback mode
 
   In data=writeback mode, ext4 does not journal data at all.  This mode provides
-  a similar level of journaling as that of XFS, JFS, and ReiserFS in its default
+  a similar level of journaling as that of XFS and JFS in its default
   mode - metadata journaling.  A crash+recovery can cause incorrect data to
   appear in files which were written shortly before the crash.  This mode will
   typically provide the best ext4 performance.
Documentation/admin-guide/laptops/laptop-mode.rst +4 -4
index b61cc601d298a8..66eb9cd918b56d 100644
@@ -61,7 +61,7 @@ Caveats
   Check your drive's rating, and don't wear down your drive's lifetime if you
   don't need to.
 
-* If you mount some of your ext3/reiserfs filesystems with the -n option, then
+* If you mount some of your ext3 filesystems with the -n option, then
   the control script will not be able to remount them correctly. You must set
   DO_REMOUNTS=0 in the control script, otherwise it will remount them with the
   wrong options -- or it will fail because it cannot write to /etc/mtab.
@@ -96,7 +96,7 @@ control script increases dirty_expire_centisecs and dirty_writeback_centisecs in
 dirtied are not forced to be written to disk as often. The control script also
 changes the dirty background ratio, so that background writeback of dirty pages
 is not done anymore. Combined with a higher commit value (also 10 minutes) for
-ext3 or ReiserFS filesystems (also done automatically by the control script),
+ext3 filesystem (also done automatically by the control script),
 this results in concentration of disk activity in a small time interval which
 occurs only once every 10 minutes, or whenever the disk is forced to spin up by
 a cache miss. The disk can then be spun down in the periods of inactivity.
@@ -587,7 +587,7 @@ Control script::
 					FST=$(deduce_fstype $MP)
 				fi
 				case "$FST" in
-					"ext3"|"reiserfs")
+					"ext3")
 						PARSEDOPTS="$(parse_mount_opts commit "$OPTS")"
 						mount $DEV -t $FST $MP -o remount,$PARSEDOPTS,commit=$MAX_AGE$NOATIME_OPT
 						;;
@@ -647,7 +647,7 @@ Control script::
 					FST=$(deduce_fstype $MP)
 				fi
 				case "$FST" in
-					"ext3"|"reiserfs")
+					"ext3")
 						PARSEDOPTS="$(parse_mount_opts_wfstab $DEV commit $OPTS)"
 						PARSEDOPTS="$(parse_yesno_opts_wfstab $DEV atime atime $PARSEDOPTS)"
 						mount $DEV -t $FST $MP -o remount,$PARSEDOPTS
Documentation/arch/powerpc/eeh-pci-error-recovery.rst +0 -1
index d6643a91bdf871..153d0af055b6da 100644
@@ -315,7 +315,6 @@ network daemons and file systems that didn't need to be disturbed.
    ideally, the reset should happen at or below the block layer,
    so that the file systems are not disturbed.
 
-   Reiserfs does not tolerate errors returned from the block device.
    Ext3fs seems to be tolerant, retrying reads/writes until it does
    succeed. Both have been only lightly tested in this scenario.
 
Documentation/translations/it_IT/process/changes.rst +0 -14
index 77db13c4022b46..7e93833b4511c0 100644
@@ -46,7 +46,6 @@ util-linux             2.10o              mount --version
 kmod                   13                 depmod -V
 e2fsprogs              1.41.4             e2fsck -V
 jfsutils               1.1.3              fsck.jfs -V
-reiserfsprogs          3.6.3              reiserfsck -V
 xfsprogs               2.6.0              xfs_db -V
 squashfs-tools         4.0                mksquashfs -version
 btrfs-progs            0.18               btrfsck
@@ -260,14 +259,6 @@ Sono disponibili i seguenti strumenti:
 
 - sono disponibili altri strumenti per il file-system.
 
-Reiserfsprogs
--------------
-
-Il pacchetto reiserfsprogs dovrebbe essere usato con reiserfs-3.6.x (Linux
-kernel 2.4.x).  Questo è un pacchetto combinato che contiene versioni
-funzionanti di ``mkreiserfs``, ``resize_reiserfs``, ``debugreiserfs`` e
-``reiserfsck``.  Questi programmi funzionano sulle piattaforme i386 e alpha.
-
 Xfsprogs
 --------
 
@@ -479,11 +470,6 @@ JFSutils
 
 - <https://jfs.sourceforge.net/>
 
-Reiserfsprogs
--------------
-
-- <https://git.kernel.org/pub/scm/linux/kernel/git/jeffm/reiserfsprogs.git/>
-
 Xfsprogs
 --------
 
fs/btrfs/tree-log.c +1 -1
index 69e11557fd13d8..b1a7cbc4fc73df 100644
@@ -5455,7 +5455,7 @@ struct btrfs_dir_list {
  * See process_dir_items_leaf() for details about why it is needed.
  * This is a recursive operation - if an existing dentry corresponds to a
  * directory, that directory's new entries are logged too (same behaviour as
- * ext3/4, xfs, f2fs, reiserfs, nilfs2). Note that when logging the inodes
+ * ext3/4, xfs, f2fs, nilfs2). Note that when logging the inodes
  * the dentries point to we do not acquire their VFS lock, otherwise lockdep
  * complains about the following circular lock dependency / possible deadlock:
  *
scripts/selinux/install_policy.sh +1 -1
index db40237e60ce7e..77368a73f11171 100755
@@ -74,7 +74,7 @@ cd /etc/selinux/dummy/contexts/files
 $SF -F file_contexts /
 
 mounts=`cat /proc/$$/mounts | \
-	grep -E "ext[234]|jfs|xfs|reiserfs|jffs2|gfs2|btrfs|f2fs|ocfs2" | \
+	grep -E "ext[234]|jfs|xfs|jffs2|gfs2|btrfs|f2fs|ocfs2" | \
 	awk '{ print $2 '}`
 $SF -F file_contexts $mounts
 
Signature · 1 line
2.50.1
#1 lore raw

Documentation/admin-guide/laptops/laptop-mode.rst Caveats · line 64

Quoted 7 lines · David Sterba

+++ b/Documentation/admin-guide/laptops/laptop-mode.rst

Documentation/admin-guide/laptops/laptop-mode.rst +1 -1
@@ -61,7 +61,7 @@ Caveats
   Check your drive's rating, and don't wear down your drive's lifetime if you
   don't need to.
 
-* If you mount some of your ext3/reiserfs filesystems with the -n option, then
+* If you mount some of your ext3 filesystems with the -n option, then

Should this be updated to ext4? ;-)

Documentation/admin-guide/laptops/laptop-mode.rst Control script:: · line 590

Quoted 6 lines
Documentation/admin-guide/laptops/laptop-mode.rst +1 -1
@@ -587,7 +587,7 @@ Control script::
 					FST=$(deduce_fstype $MP)
 				fi
 				case "$FST" in
-					"ext3"|"reiserfs")
+					"ext3")

... uh. Maybe much more significant work is needed ;-)

Documentation/arch/powerpc/eeh-pci-error-recovery.rst network daemons and file systems that didn't need to be disturbed. · line 319

Quoted 8 lines
Documentation/arch/powerpc/eeh-pci-error-recovery.rst +1 -1
+++ b/Documentation/arch/powerpc/eeh-pci-error-recovery.rst
@@ -315,7 +315,6 @@ network daemons and file systems that didn't need to be disturbed.
    ideally, the reset should happen at or below the block layer,
    so that the file systems are not disturbed.
 
-   Reiserfs does not tolerate errors returned from the block device.
    Ext3fs seems to be tolerant, retrying reads/writes until it does
    succeed. Both have been only lightly tested in this scenario.

"Both" is now orphaned with the removal of ReiserFS. And the ext3 sentence has an implicit reference to "errors returned from the block device" that is now missing. A wider change is needed here.

#2 lore raw
Quoted 25 lines · Matthew Wilcox

Documentation/admin-guide/laptops/laptop-mode.rst Caveats · line 64

Quoted 7 lines · David Sterba

+++ b/Documentation/admin-guide/laptops/laptop-mode.rst

Documentation/admin-guide/laptops/laptop-mode.rst +1 -1
@@ -61,7 +61,7 @@ Caveats
   Check your drive's rating, and don't wear down your drive's lifetime if you
   don't need to.
 
-* If you mount some of your ext3/reiserfs filesystems with the -n option, then
+* If you mount some of your ext3 filesystems with the -n option, then

Should this be updated to ext4? ;-)

Documentation/admin-guide/laptops/laptop-mode.rst Control script:: · line 590

Quoted 6 lines
Documentation/admin-guide/laptops/laptop-mode.rst +1 -1
@@ -587,7 +587,7 @@ Control script::
 					FST=$(deduce_fstype $MP)
 				fi
 				case "$FST" in
-					"ext3"|"reiserfs")
+					"ext3")

... uh. Maybe much more significant work is needed ;-)

Quoted 5 lines
Documentation/arch/powerpc/eeh-pci-error-recovery.rst +1 -0
+++ b/Documentation/arch/powerpc/eeh-pci-error-recovery.rst
@@ -315,7 +315,6 @@ network daemons and file systems that didn't need to be disturbed.
    ideally, the reset should happen at or below the block layer,
    so that the file systems are not disturbed.
 
Quoted 7 lines

Documentation/arch/powerpc/eeh-pci-error-recovery.rst network daemons and file systems that didn't need to be disturbed. · line 319

Quoted 3 lines
Documentation/arch/powerpc/eeh-pci-error-recovery.rst +0 -1
-   Reiserfs does not tolerate errors returned from the block device.
    Ext3fs seems to be tolerant, retrying reads/writes until it does
    succeed. Both have been only lightly tested in this scenario.

"Both" is now orphaned with the removal of ReiserFS. And the ext3 sentence has an implicit reference to "errors returned from the block device" that is now missing. A wider change is needed here.

Yes, the ext3 mentions stand out in the documentation. I don't think it could be changed to ext4 in all places, there's a mix of historical references, quotes and 'scripts in documentation'.

maintainer
#3 lore raw
In reply to David Sterba
Quoted 17 lines · David Sterba

Reiserfs has been removed in 6.13, there are still some mentions in the documentation about it and the tools. Remove those that don't seem relevant anymore but keep references to reiserfs' r5 hash used by some code.

There's one change in a script scripts/selinux/install_policy.sh but it does not seem to be relevant either.

---

scripts/selinux/install_policy.sh +0 -0
index db40237e60ce7e..77368a73f11171 100755

scripts/selinux/install_policy.sh cd /etc/selinux/dummy/contexts/files · line 80

Quoted 8 lines
scripts/selinux/install_policy.sh +1 -1
@@ -74,7 +74,7 @@ cd /etc/selinux/dummy/contexts/files
 $SF -F file_contexts /
 
 mounts=`cat /proc/$$/mounts | \
-       grep -E "ext[234]|jfs|xfs|reiserfs|jffs2|gfs2|btrfs|f2fs|ocfs2" | \
+       grep -E "ext[234]|jfs|xfs|jffs2|gfs2|btrfs|f2fs|ocfs2" | \
        awk '{ print $2 '}`
 $SF -F file_contexts $mounts
 

Just commenting on the selinux part, this entire list of filesystem types could likely be removed and replaced by just running "fixfiles relabel" instead, which on modern kernels (>= 2.6.30) will check for the "seclabel" option in /proc/self/mounts entries to determine which filesystems support security labeling.

maintainer Acked-by
#4 lore raw
Quoted 20 lines · Stephen Smalley
Quoted 19 lines · David Sterba

Reiserfs has been removed in 6.13, there are still some mentions in the documentation about it and the tools. Remove those that don't seem relevant anymore but keep references to reiserfs' r5 hash used by some code.

There's one change in a script scripts/selinux/install_policy.sh but it does not seem to be relevant either.

---

scripts/selinux/install_policy.sh +0 -0
index db40237e60ce7e..77368a73f11171 100755
@@ -74,7 +74,7 @@ cd /etc/selinux/dummy/contexts/files
 $SF -F file_contexts /
 
Quoted 12 lines

scripts/selinux/install_policy.sh cd /etc/selinux/dummy/contexts/files · line 80

Quoted 6 lines
scripts/selinux/install_policy.sh +1 -1
 mounts=`cat /proc/$$/mounts | \
-       grep -E "ext[234]|jfs|xfs|reiserfs|jffs2|gfs2|btrfs|f2fs|ocfs2" | \
+       grep -E "ext[234]|jfs|xfs|jffs2|gfs2|btrfs|f2fs|ocfs2" | \
        awk '{ print $2 '}`
 $SF -F file_contexts $mounts
 

Just commenting on the selinux part, this entire list of filesystem types could likely be removed and replaced by just running "fixfiles relabel" instead, which on modern kernels (>= 2.6.30) will check for the "seclabel" option in /proc/self/mounts entries to determine which filesystems support security labeling.

... but in the meantime this patch looks fine.

Signature · 1 line
paul-moore.com
maintainer
#5 lore raw
In reply to David Sterba
Quoted 9 lines · David Sterba

Reiserfs has been removed in 6.13, there are still some mentions in the documentation about it and the tools. Remove those that don't seem relevant anymore but keep references to reiserfs' r5 hash used by some code.

There's one change in a script scripts/selinux/install_policy.sh but it does not seem to be relevant either.

Quoted 8 lines
---
 Documentation/admin-guide/ext4.rst                 |  2 +-
 Documentation/admin-guide/laptops/laptop-mode.rst  |  8 ++++----
 .../arch/powerpc/eeh-pci-error-recovery.rst        |  1 -
 .../translations/it_IT/process/changes.rst         | 14 --------------
 fs/btrfs/tree-log.c                                |  2 +-
 scripts/selinux/install_policy.sh                  |  2 +-
 6 files changed, 7 insertions(+), 22 deletions(-)

It seems there is more that could be done here, but I have applied this as a step forward.

Thanks,

jon