From nobody Sat Oct 4 19:16:48 2025 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.223.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5A2542BEFFF for ; Wed, 13 Aug 2025 10:00:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=195.135.223.131 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755079259; cv=none; b=Iu1KnZdw77fmtK+axgf6hfYOxUSDo3Ll/zM/hl2OUDMaLgYsAwWwcVXAMIZShJM0CZe471miQgoWXiv59XfG+SvVlvxOpsKC9hWGth2yecDHW7XEh3IFNgJa/fE3yisEx+tA4/yQlF88y/amFPGn72iRaDHcbJC7m27YvniocAg= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755079259; c=relaxed/simple; bh=lPbDKB+k3lVOg0NIqRZqCdG2ByUO9olATiDAqVwQH64=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type; b=ZxrVmHt7gWiOhO+f2xZ7FCcpMdhFuLYfJfO1bFCkSBiY9DNhxtNYuxcQchZcPIuG+d2IltbQboY5/XNv823VLJrVDHzYWXup3YFpEtbR0h6Q7NRszkOUWiyW8aPMwStEa2GsBXXRSG0d8pvi8Nekw8DckmeW/UIVc+JJ6OVuRCU= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=suse.com; spf=pass smtp.mailfrom=suse.com; dkim=pass (1024-bit key) header.d=suse.com header.i=@suse.com header.b=u5/WqcO2; dkim=pass (1024-bit key) header.d=suse.com header.i=@suse.com header.b=u5/WqcO2; arc=none smtp.client-ip=195.135.223.131 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=suse.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=suse.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=suse.com header.i=@suse.com header.b="u5/WqcO2"; dkim=pass (1024-bit key) header.d=suse.com header.i=@suse.com header.b="u5/WqcO2" Received: from imap1.dmz-prg2.suse.org (unknown [10.150.64.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 5FCB91F455; Wed, 13 Aug 2025 10:00:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1755079255; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=5UhIUEj2H0HZtJwL7CC3eT7YVhReTUM/dByrOfvrPPE=; b=u5/WqcO2Uv1NDP40/A6xjiDIpQkWZHygrA5J5mcApuysq8OZJ0ludDnKcT+Tt0HsjSlTRm ablbkn9wZZiTVR66cOY+OvXGAxeRmIwstLr+o1iSFXQZiecHadUpoa1oRYtzseWBcl7Btq rmqzn1Yud0PYLLV8YPNxe7ZMyIEdCgA= Authentication-Results: smtp-out2.suse.de; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1755079255; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=5UhIUEj2H0HZtJwL7CC3eT7YVhReTUM/dByrOfvrPPE=; b=u5/WqcO2Uv1NDP40/A6xjiDIpQkWZHygrA5J5mcApuysq8OZJ0ludDnKcT+Tt0HsjSlTRm ablbkn9wZZiTVR66cOY+OvXGAxeRmIwstLr+o1iSFXQZiecHadUpoa1oRYtzseWBcl7Btq rmqzn1Yud0PYLLV8YPNxe7ZMyIEdCgA= Received: from imap1.dmz-prg2.suse.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by imap1.dmz-prg2.suse.org (Postfix) with ESMTPS id 58B3F13929; Wed, 13 Aug 2025 10:00:55 +0000 (UTC) Received: from dovecot-director2.suse.de ([2a07:de40:b281:106:10:150:64:167]) by imap1.dmz-prg2.suse.org with ESMTPSA id M5GhFVdinGj1IgAAD6G6ig (envelope-from ); Wed, 13 Aug 2025 10:00:55 +0000 From: David Sterba To: linux-doc@vger.kernel.org Cc: Jonathan Corbet , Ondrej Mosnacek , Paul Moore , selinux@vger.kernel.org, linux-kernel@vger.kernel.org, David Sterba Subject: [PATCH] docs: Remove remainders of reiserfs Date: Wed, 13 Aug 2025 12:00:52 +0200 Message-ID: <20250813100053.1291961-1-dsterba@suse.com> X-Mailer: git-send-email 2.50.1 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-3.30 / 50.00]; BAYES_HAM(-3.00)[100.00%]; MID_CONTAINS_FROM(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.20)[-0.998]; MIME_GOOD(-0.10)[text/plain]; FUZZY_RATELIMITED(0.00)[rspamd.com]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; RCPT_COUNT_SEVEN(0.00)[7]; DKIM_SIGNED(0.00)[suse.com:s=susede1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DBL_BLOCKED_OPENRESOLVER(0.00)[suse.com:mid,suse.com:email,imap1.dmz-prg2.suse.org:helo] X-Spam-Flag: NO X-Spam-Level: X-Spam-Score: -3.30 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 Acked-by: Paul Moore --- 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 =20 In data=3Dwriteback 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 d= efault + 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/Documentat= ion/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. =20 -* 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=3D0 in the control script, otherwise it will remount them wi= th 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 scrip= t), +ext3 filesystem (also done automatically by the control script), this results in concentration of disk activity in a small time interval wh= ich 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=3D$(deduce_fstype $MP) fi case "$FST" in - "ext3"|"reiserfs") + "ext3") PARSEDOPTS=3D"$(parse_mount_opts commit "$OPTS")" mount $DEV -t $FST $MP -o remount,$PARSEDOPTS,commit=3D$MAX_AGE$NOAT= IME_OPT ;; @@ -647,7 +647,7 @@ Control script:: FST=3D$(deduce_fstype $MP) fi case "$FST" in - "ext3"|"reiserfs") + "ext3") PARSEDOPTS=3D"$(parse_mount_opts_wfstab $DEV commit $OPTS)" PARSEDOPTS=3D"$(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/Docume= ntation/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. =20 - 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. =20 diff --git a/Documentation/translations/it_IT/process/changes.rst b/Documen= tation/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: =20 - sono disponibili altri strumenti per il file-system. =20 -Reiserfsprogs -------------- - -Il pacchetto reiserfsprogs dovrebbe essere usato con reiserfs-3.6.x (Linux -kernel 2.4.x). Questo =C3=A8 un pacchetto combinato che contiene versioni -funzionanti di ``mkreiserfs``, ``resize_reiserfs``, ``debugreiserfs`` e -``reiserfsck``. Questi programmi funzionano sulle piattaforme i386 e alph= a. - Xfsprogs -------- =20 @@ -479,11 +470,6 @@ JFSutils =20 - =20 -Reiserfsprogs -------------- - -- - Xfsprogs -------- =20 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 lockd= ep * complains about the following circular lock dependency / possible deadl= ock: * diff --git a/scripts/selinux/install_policy.sh b/scripts/selinux/install_po= licy.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 / =20 mounts=3D`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 =20 --=20 2.50.1