Linux filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Agamalt 10 <agamalt10@gmail.com>, David Sterba <dsterba@suse.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: URGENT BUGS TO FIX IN THE FILE SYSTEM, KERNEL PANICS, INT OVERFLOWS, ETC.
Date: Thu, 30 Jul 2026 19:37:20 +0200	[thread overview]
Message-ID: <20260730173719.GU10684@suse.cz> (raw)
In-Reply-To: <CAHk-=wjrds=Xi4SrMQocb7_kF5eyi0WOUbJ7Lb3bBbRf9gTvoQ@mail.gmail.com>

On Wed, Jul 29, 2026 at 05:15:46PM -0700, Linus Torvalds wrote:
> Please do proper kernel bug reporting, which means "don't just sent to
> Linus", but figure out the maintainer etc. We have documentation about
> this all.
> 
> That filesystem isn't a serious filesystem, and that code needs a lot
> more fixing if somebody cares.
> 
> Instead of doing
> 
>         if (affs_validblock(sb, block)) {
>                 bh = sb_getblk(sb, block);
> 
> it should probably just do
> 
>         bh = affs_getblk(sb, block);
>         if (bh) {
> 
> instead, but honestly, I can't find it in myself to care about an
> unlikely error case that nobody has ever seen and reported, all in a
> legacy Amiga filesystem that nobody really uses outside of hobby Amiga
> enthusiasts.
> 
> But we do have a listed sucker^Hmaintainer for it that says "Odd
> Fixes", and this certainly counts as an odd fix.
> 
> So I'm cc'ing David and fsdevel in case there is somebody else with an
> Amiga background.

Thanks, I have a few more pending AFFS fixes, but nothing serious so
it's in the backlog. The last fix from the community was in 2020
d3a84a8d0dde4e ("affs: fix basic permission bits to actually work"). The
rest is tree-wide and recently the AI assisted reports.

> Me, I'm still bitter about those rich kids with their fancy sprites on
> their Amiga HW, which may be one reason I don't feel like fixing the
> problems in AFFS ;)

For me it was only a ZX Spectrum on a grayscale 12" TV, blissfully unaware.

      reply	other threads:[~2026-07-30 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMwtO3LAzbJHZXixDbYD-LGu2qe5P4zVQBD4fsqNr-P3wzAZUg@mail.gmail.com>
2026-07-30  0:15 ` URGENT BUGS TO FIX IN THE FILE SYSTEM, KERNEL PANICS, INT OVERFLOWS, ETC Linus Torvalds
2026-07-30 17:37   ` David Sterba [this message]

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=20260730173719.GU10684@suse.cz \
    --to=dsterba@suse.cz \
    --cc=agamalt10@gmail.com \
    --cc=dsterba@suse.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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