linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Matthew Wilcox <willy@infradead.org>
Cc: David Sterba <dsterba@suse.com>,
	linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Ondrej Mosnacek <omosnace@redhat.com>,
	Paul Moore <paul@paul-moore.com>,
	selinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: Remove remainders of reiserfs
Date: Thu, 14 Aug 2025 13:33:37 +0200	[thread overview]
Message-ID: <20250814113337.GD22430@suse.cz> (raw)
In-Reply-To: <aJyQcAyOrp45D84g@casper.infradead.org>

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'.

  reply	other threads:[~2025-08-14 11:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2025-08-13 15:43 ` Stephen Smalley
2025-08-13 16:04   ` Paul Moore
2025-08-18 16:46 ` Jonathan Corbet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250814113337.GD22430@suse.cz \
    --to=dsterba@suse.cz \
    --cc=corbet@lwn.net \
    --cc=dsterba@suse.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=omosnace@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=selinux@vger.kernel.org \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).