mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Matthew Wilcox <willy@infradead.org>,
	Ben Dooks <ben-linux-arm@fluff.org>,
	Stuart Swales <stuart.swales.croftnuisk@gmail.com>
Subject: fs/adfs - keep or kill it?
Date: Thu, 4 Apr 2019 11:35:21 +0100	[thread overview]
Message-ID: <20190404103521.pklwk4efp2zccjzc@shell.armlinux.org.uk> (raw)

Hi,

Recently, a couple of issues have been identified in fs/adfs:

1. Filename truncation may not work as it should, and Linus has
   apparently expressed a desire to kill this off.

2. Scanning the ADFS map for disc object fragments may mistakenly
   find free space fragments in addition to real disc object fragments,
   leading to chunks of free space appearing in files or directories.

No one has reported any issues with the filesystem module, so the
question has to be asked whether there are any users of this code?

I'm aware that there were some users about ten or more years ago.  I've
only touched it when problems have been reported to me that needed me
to investigate something, otherwise I haven't used it myself - so the
code largely just sits there, mostly untouched except for the odd
cross-filesystem patch.

The last "feature" patch was in 2011 by Stuart Swales (copied) adding
the filetype suffix to filenames.

That leads on to the question about whether this should be fixed in
mainline or whether we should put the code out of its misery and remove
it from the kernel.

Fixing both issues is fairly trivial, and I already have some fixes
available, along with some improvements to the rest of the code.
However, I see little point in pushing that upstream if the code is
not being used.

Searching the web, there does seem to be some interest on some forums,
but that dates from about three years ago, but it also seems that more
functional solutions (using fuse, with different format support) are
available.

Posting to Linux lists probably isn't the best way to find out whether
there are users of this, so if there are people involved in the Acorn
communities, please pass this on to more appropriate forums, thanks.
Please ensure that replies reach me as I don't monitor random web
forums for example (a reply on a web forum that I don't see is not
helpful.)

If I hear nothing positive towards keeping it, then I'll schedule
fs/adfs for deletion, probably for 5.3.

Thanks.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up

             reply	other threads:[~2019-04-04 10:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 10:35 Russell King - ARM Linux admin [this message]
2019-04-04 20:44 ` Stuart Swales
2019-04-04 20:55   ` Matthew Wilcox

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=20190404103521.pklwk4efp2zccjzc@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=ben-linux-arm@fluff.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stuart.swales.croftnuisk@gmail.com \
    --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

all inboxes | Powered by JetHome®