From: Arnd Bergmann <arnd@arndb.de>
To: Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/14] Fix HPFS
Date: Thu, 19 May 2011 16:42:00 +0200 [thread overview]
Message-ID: <201105191642.00233.arnd@arndb.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1105082019230.7013@artax.karlin.mff.cuni.cz>
On Sunday 08 May 2011, Mikulas Patocka wrote:
> This series of patches fixes the HPFS filesystem in 2.6.39. HPFS was
> broken in 2.6.39-rc1 due to big kernel lock removal. These patches also
> make it portable, I tested it on big endian machines.
Thanks for picking it up again after I made it UP-only!
> BTW. would you also like to commit my another filesystem (SpadFS) to the
> Linux kernel? It is at
> http://artax.karlin.mff.cuni.cz/~mikulas/spadfs/download/spadfs-0.9.12.tar.gz
> It is very small (300kB), it uses crash counts instead of journaling to
> keep itself consistent, it stores inodes directly in directories, saving
> one seek on opening files and it uses extendible hashing for directory
> organization.
There is a nonzero maintainance overhead that comes with every file
system getting added to the kernel, plus the pain that comes with
potential security problems and maintaining backwards compatibility
with an installed user base. 300kb is not extremely small for a
new file system either, it's actually slightly larger than ext2.
If you can provide a convincing argument why the code is useful
to other people and what it does that no other file system today
can do, we can start looking at the patch. My initial impression
from looking at it is that it's fairly clean code, I'm just missing
the point of why I would want to use it.
Arnd
prev parent reply other threads:[~2011-05-19 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 18:42 [PATCH 0/14] Fix HPFS Mikulas Patocka
2011-05-19 14:42 ` Arnd Bergmann [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=201105191642.00233.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--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