* [PATCH] docs: Remove remainders of reiserfs
@ 2025-08-13 10:00 David Sterba
2025-08-13 13:17 ` Matthew Wilcox
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: David Sterba @ 2025-08-13 10:00 UTC (permalink / raw)
To: linux-doc
Cc: Jonathan Corbet, Ondrej Mosnacek, Paul Moore, selinux,
linux-kernel, 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.
Signed-off-by: David Sterba <dsterba@suse.com>
---
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(-)
diff --git a/Documentation/admin-guide/ext4.rst b/Documentation/admin-guide/ext4.rst
index b857eb6ca1b620..ac0c709ea9e7c1 100644
--- a/Documentation/admin-guide/ext4.rst
+++ b/Documentation/admin-guide/ext4.rst
@@ -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.
diff --git a/Documentation/admin-guide/laptops/laptop-mode.rst b/Documentation/admin-guide/laptops/laptop-mode.rst
index b61cc601d298a8..66eb9cd918b56d 100644
--- a/Documentation/admin-guide/laptops/laptop-mode.rst
+++ b/Documentation/admin-guide/laptops/laptop-mode.rst
@@ -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
diff --git a/Documentation/arch/powerpc/eeh-pci-error-recovery.rst b/Documentation/arch/powerpc/eeh-pci-error-recovery.rst
index d6643a91bdf871..153d0af055b6da 100644
--- a/Documentation/arch/powerpc/eeh-pci-error-recovery.rst
+++ 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.
diff --git a/Documentation/translations/it_IT/process/changes.rst b/Documentation/translations/it_IT/process/changes.rst
index 77db13c4022b46..7e93833b4511c0 100644
--- a/Documentation/translations/it_IT/process/changes.rst
+++ b/Documentation/translations/it_IT/process/changes.rst
@@ -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
--------
diff --git a/fs/btrfs/tree-log.c b/fs/btrfs/tree-log.c
index 69e11557fd13d8..b1a7cbc4fc73df 100644
--- a/fs/btrfs/tree-log.c
+++ b/fs/btrfs/tree-log.c
@@ -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:
*
diff --git a/scripts/selinux/install_policy.sh b/scripts/selinux/install_policy.sh
index db40237e60ce7e..77368a73f11171 100755
--- a/scripts/selinux/install_policy.sh
+++ b/scripts/selinux/install_policy.sh
@@ -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
--
2.50.1
^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: [PATCH] docs: Remove remainders of reiserfs
2025-08-13 10:00 [PATCH] docs: Remove remainders of reiserfs David Sterba
@ 2025-08-13 13:17 ` Matthew Wilcox
2025-08-14 11:33 ` David Sterba
2025-08-13 15:43 ` Stephen Smalley
2025-08-18 16:46 ` Jonathan Corbet
2 siblings, 1 reply; 6+ messages in thread
From: Matthew Wilcox @ 2025-08-13 13:17 UTC (permalink / raw)
To: David Sterba
Cc: linux-doc, Jonathan Corbet, Ondrej Mosnacek, Paul Moore, selinux,
linux-kernel
On Wed, Aug 13, 2025 at 12:00:52PM +0200, David Sterba wrote:
> +++ b/Documentation/admin-guide/laptops/laptop-mode.rst
> @@ -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? ;-)
> @@ -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 ;-)
> +++ 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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] docs: Remove remainders of reiserfs
2025-08-13 10:00 [PATCH] docs: Remove remainders of reiserfs David Sterba
2025-08-13 13:17 ` Matthew Wilcox
@ 2025-08-13 15:43 ` Stephen Smalley
2025-08-13 16:04 ` Paul Moore
2025-08-18 16:46 ` Jonathan Corbet
2 siblings, 1 reply; 6+ messages in thread
From: Stephen Smalley @ 2025-08-13 15:43 UTC (permalink / raw)
To: David Sterba
Cc: linux-doc, Jonathan Corbet, Ondrej Mosnacek, Paul Moore, selinux,
linux-kernel
On Wed, Aug 13, 2025 at 6:04 AM David Sterba <dsterba@suse.com> wrote:
>
> 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.
>
> Signed-off-by: David Sterba <dsterba@suse.com>
> ---
> diff --git a/scripts/selinux/install_policy.sh b/scripts/selinux/install_policy.sh
> index db40237e60ce7e..77368a73f11171 100755
> --- a/scripts/selinux/install_policy.sh
> +++ b/scripts/selinux/install_policy.sh
> @@ -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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] docs: Remove remainders of reiserfs
2025-08-13 15:43 ` Stephen Smalley
@ 2025-08-13 16:04 ` Paul Moore
0 siblings, 0 replies; 6+ messages in thread
From: Paul Moore @ 2025-08-13 16:04 UTC (permalink / raw)
To: Stephen Smalley
Cc: David Sterba, linux-doc, Jonathan Corbet, Ondrej Mosnacek,
selinux, linux-kernel
On Wed, Aug 13, 2025 at 11:43 AM Stephen Smalley
<stephen.smalley.work@gmail.com> wrote:
> On Wed, Aug 13, 2025 at 6:04 AM David Sterba <dsterba@suse.com> wrote:
> >
> > 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.
> >
> > Signed-off-by: David Sterba <dsterba@suse.com>
> > ---
>
> > diff --git a/scripts/selinux/install_policy.sh b/scripts/selinux/install_policy.sh
> > index db40237e60ce7e..77368a73f11171 100755
> > --- a/scripts/selinux/install_policy.sh
> > +++ b/scripts/selinux/install_policy.sh
> > @@ -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.
... but in the meantime this patch looks fine.
Acked-by: Paul Moore <paul@paul-moore.com>
--
paul-moore.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] docs: Remove remainders of reiserfs
2025-08-13 13:17 ` Matthew Wilcox
@ 2025-08-14 11:33 ` David Sterba
0 siblings, 0 replies; 6+ messages in thread
From: David Sterba @ 2025-08-14 11:33 UTC (permalink / raw)
To: Matthew Wilcox
Cc: David Sterba, linux-doc, Jonathan Corbet, Ondrej Mosnacek,
Paul Moore, selinux, linux-kernel
On Wed, Aug 13, 2025 at 02:17:36PM +0100, Matthew Wilcox wrote:
> On Wed, Aug 13, 2025 at 12:00:52PM +0200, David Sterba wrote:
> > +++ b/Documentation/admin-guide/laptops/laptop-mode.rst
> > @@ -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? ;-)
>
> > @@ -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 ;-)
>
> > +++ 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.
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'.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] docs: Remove remainders of reiserfs
2025-08-13 10:00 [PATCH] docs: Remove remainders of reiserfs David Sterba
2025-08-13 13:17 ` Matthew Wilcox
2025-08-13 15:43 ` Stephen Smalley
@ 2025-08-18 16:46 ` Jonathan Corbet
2 siblings, 0 replies; 6+ messages in thread
From: Jonathan Corbet @ 2025-08-18 16:46 UTC (permalink / raw)
To: David Sterba, linux-doc
Cc: Ondrej Mosnacek, Paul Moore, selinux, linux-kernel, David Sterba
David Sterba <dsterba@suse.com> writes:
> 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.
>
> Signed-off-by: David Sterba <dsterba@suse.com>
> ---
> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2025-08-18 16:46 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-08-13 10:00 [PATCH] docs: Remove remainders of reiserfs David Sterba
2025-08-13 13:17 ` Matthew Wilcox
2025-08-14 11:33 ` David Sterba
2025-08-13 15:43 ` Stephen Smalley
2025-08-13 16:04 ` Paul Moore
2025-08-18 16:46 ` Jonathan Corbet
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).