linux-kernel - Re: moving affs + RDB partition support to staging?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180426105940.smn3447igebe5r34@twin.jikos.cz>
Date:   Thu, 26 Apr 2018 12:59:40 +0200
From:   David Sterba <dsterba@...e.cz>
To:     John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
Cc:     Martin Steigerwald <martin@...htvoll.de>,
        Matthew Wilcox <willy@...radead.org>, dsterba@...e.cz,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        Jens Axboe <axboe@...nel.dk>, linux-m68k@...r.kernel.org,
        Debian m68k <debian-68k@...ts.debian.org>
Subject: Re: moving affs + RDB partition support to staging?

On Thu, Apr 26, 2018 at 12:45:41PM +0200, John Paul Adrian Glaubitz wrote:
> (adding debian-68k)
> 
> Hi Matthew!
> 
> On 04/26/2018 12:28 PM, Martin Steigerwald wrote:
> > You probably put your stick into a cave with ancient sleeping dragons :)
> 
> Indeed.
> 
> > Added in linux-m68k mailing list, as they likely have an opinion on how
> > to treat affs + RDB partition support. Also added in Jens Axboe about
> > patching that RDB support broken with 2 TB or larger harddisks issue
> > which had been in Linux kernel for 6 years while a patch exists that to
> > my testing back then solves the issue.
> 
> The answer is that we are still very much actively using RDB and AFFS
> supoort in the Linux kernel and if you were to remove it, you would
> directly hit users.

Based on that I think removing affs will not happen, but the upstream
maintenance status should be updated accordingly.

> I know it may sound crazy, but the Linux/m68k port (Atari, Mac, Amiga etc)
> is a very actively used and maintained port which just recently received
> three new drivers:
> 
> > https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue&id=3109e5ae0311e937d49a5325134e50b742ac5f4a
> > https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=861928f4e60e826cd8871c0c37f4b3d825b8d81d
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/ata/pata_gayle.c?id=9ab27d1d35fda0c5fce624083e92546a8545e7e5
> 
> The community around the m68k CPU is constantly developing new hardware
> (new accelerator boards, networking cards, IDE controllers etc for the
> Amiga and so on). So, the community and the port are anything but dead.
> 
> > > Yeah, it's pretty sad how few commits some of these filesystems have
> > > had in recent years.  One can argue that they're stable and don't need
> > > to be fixed because they aren't broken, but I find it hard to believe
> > > that any of them were better-implemented than ext2 which still sees
> > > regular bugfixes.
> 
> Exactly. It works fine as is:
...
> There is nothing at the moment that needs fixing.

So, I'm willing to act as upstream maintainer for affs, send pull
requests with fixes if you ever need that (unless you find someone
else).