linux-kernel - Re: LogFS merge

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: <alpine.LFD.1.10.0805021438180.5994@woody.linux-foundation.org>
Date:	Fri, 2 May 2008 14:39:23 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jörn Engel <joern@...fs.org>
cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Andrew Morton <akpm@...ux-foundation.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org
Subject: Re: LogFS merge



On Fri, 2 May 2008, Jörn Engel wrote:
>
> I have a solution for this, but it would require an incompatible change
> to the format.  And right now I have fairly good confidence in the
> format wrt. ensuring correctness.  So the plan is to merge logfs as-is
> (modulo bugfixes, review fallout, etc.) and handle the changes for this
> and other performance problems with compat flags.  And someday rename
> the whole mess to log2fs and remove some support for old format
> variants.

Quite frankly, if that's the case, I'd *much* rather see that worked on 
first, so that there aren't any format changes that are already known to 
be pending before it even gets merged.

Would it be at all possible to try to do that, or is it just "too far 
out"?

		Linus
--
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/