[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aJyQcAyOrp45D84g@casper.infradead.org>
Date: Wed, 13 Aug 2025 14:17:36 +0100
From: Matthew Wilcox <willy@...radead.org>
To: David Sterba <dsterba@...e.com>
Cc: linux-doc@...r.kernel.org, Jonathan Corbet <corbet@....net>,
Ondrej Mosnacek <omosnace@...hat.com>,
Paul Moore <paul@...l-moore.com>, selinux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: Remove remainders of reiserfs
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.
Powered by blists - more mailing lists