linux-kernel - Re: [PATCH 0/14] Fix HPFS

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] [day] [month] [year] [list]

Date:	Thu, 19 May 2011 16:42:00 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 0/14] Fix HPFS

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/