Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
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.
Signed-off-by: David Sterba <dsterba@suse.com>
Acked-by: Paul Moore <paul@paul-moore.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20250813100053.1291961-1-dsterba@suse.com
authored by
David Sterba
and committed by
Jonathan Corbet
37c52167
4e18a0b0
+7
-22
+1
-1
Documentation/admin-guide/ext4.rst
+1
-1
Documentation/admin-guide/ext4.rst
···
398
398
* writeback mode
399
399
400
400
In data=writeback mode, ext4 does not journal data at all. This mode provides
401
-
a similar level of journaling as that of XFS, JFS, and ReiserFS in its default
401
+
a similar level of journaling as that of XFS and JFS in its default
402
402
mode - metadata journaling. A crash+recovery can cause incorrect data to
403
403
appear in files which were written shortly before the crash. This mode will
404
404
typically provide the best ext4 performance.
+4
-4
Documentation/admin-guide/laptops/laptop-mode.rst
+4
-4
Documentation/admin-guide/laptops/laptop-mode.rst
···
61
61
Check your drive's rating, and don't wear down your drive's lifetime if you
62
62
don't need to.
63
63
64
-
* If you mount some of your ext3/reiserfs filesystems with the -n option, then
64
+
* If you mount some of your ext3 filesystems with the -n option, then
65
65
the control script will not be able to remount them correctly. You must set
66
66
DO_REMOUNTS=0 in the control script, otherwise it will remount them with the
67
67
wrong options -- or it will fail because it cannot write to /etc/mtab.
···
96
96
dirtied are not forced to be written to disk as often. The control script also
97
97
changes the dirty background ratio, so that background writeback of dirty pages
98
98
is not done anymore. Combined with a higher commit value (also 10 minutes) for
99
-
ext3 or ReiserFS filesystems (also done automatically by the control script),
99
+
ext3 filesystem (also done automatically by the control script),
100
100
this results in concentration of disk activity in a small time interval which
101
101
occurs only once every 10 minutes, or whenever the disk is forced to spin up by
102
102
a cache miss. The disk can then be spun down in the periods of inactivity.
···
587
587
FST=$(deduce_fstype $MP)
588
588
fi
589
589
case "$FST" in
590
-
"ext3"|"reiserfs")
590
+
"ext3")
591
591
PARSEDOPTS="$(parse_mount_opts commit "$OPTS")"
592
592
mount $DEV -t $FST $MP -o remount,$PARSEDOPTS,commit=$MAX_AGE$NOATIME_OPT
593
593
;;
···
647
647
FST=$(deduce_fstype $MP)
648
648
fi
649
649
case "$FST" in
650
-
"ext3"|"reiserfs")
650
+
"ext3")
651
651
PARSEDOPTS="$(parse_mount_opts_wfstab $DEV commit $OPTS)"
652
652
PARSEDOPTS="$(parse_yesno_opts_wfstab $DEV atime atime $PARSEDOPTS)"
653
653
mount $DEV -t $FST $MP -o remount,$PARSEDOPTS
-1
Documentation/arch/powerpc/eeh-pci-error-recovery.rst
-1
Documentation/arch/powerpc/eeh-pci-error-recovery.rst
···
315
315
ideally, the reset should happen at or below the block layer,
316
316
so that the file systems are not disturbed.
317
317
318
-
Reiserfs does not tolerate errors returned from the block device.
319
318
Ext3fs seems to be tolerant, retrying reads/writes until it does
320
319
succeed. Both have been only lightly tested in this scenario.
321
320
-14
Documentation/translations/it_IT/process/changes.rst
-14
Documentation/translations/it_IT/process/changes.rst
···
46
46
kmod 13 depmod -V
47
47
e2fsprogs 1.41.4 e2fsck -V
48
48
jfsutils 1.1.3 fsck.jfs -V
49
-
reiserfsprogs 3.6.3 reiserfsck -V
50
49
xfsprogs 2.6.0 xfs_db -V
51
50
squashfs-tools 4.0 mksquashfs -version
52
51
btrfs-progs 0.18 btrfsck
···
259
260
260
261
- sono disponibili altri strumenti per il file-system.
261
262
262
-
Reiserfsprogs
263
-
-------------
264
-
265
-
Il pacchetto reiserfsprogs dovrebbe essere usato con reiserfs-3.6.x (Linux
266
-
kernel 2.4.x). Questo è un pacchetto combinato che contiene versioni
267
-
funzionanti di ``mkreiserfs``, ``resize_reiserfs``, ``debugreiserfs`` e
268
-
``reiserfsck``. Questi programmi funzionano sulle piattaforme i386 e alpha.
269
-
270
263
Xfsprogs
271
264
--------
272
265
···
469
478
--------
470
479
471
480
- <https://jfs.sourceforge.net/>
472
-
473
-
Reiserfsprogs
474
-
-------------
475
-
476
-
- <https://git.kernel.org/pub/scm/linux/kernel/git/jeffm/reiserfsprogs.git/>
477
481
478
482
Xfsprogs
479
483
--------
+1
-1
fs/btrfs/tree-log.c
+1
-1
fs/btrfs/tree-log.c
···
5460
5460
* See process_dir_items_leaf() for details about why it is needed.
5461
5461
* This is a recursive operation - if an existing dentry corresponds to a
5462
5462
* directory, that directory's new entries are logged too (same behaviour as
5463
-
* ext3/4, xfs, f2fs, reiserfs, nilfs2). Note that when logging the inodes
5463
+
* ext3/4, xfs, f2fs, nilfs2). Note that when logging the inodes
5464
5464
* the dentries point to we do not acquire their VFS lock, otherwise lockdep
5465
5465
* complains about the following circular lock dependency / possible deadlock:
5466
5466
*
+1
-1
scripts/selinux/install_policy.sh
+1
-1
scripts/selinux/install_policy.sh