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]

Date:	Sat, 3 May 2008 09:03:18 +0200
From:	Willy Tarreau <w@....eu>
To:	Jörn Engel <joern@...fs.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	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, May 02, 2008 at 11:58:33PM +0200, Jörn Engel wrote:
> On Fri, 2 May 2008 14:39:23 -0700, Linus Torvalds wrote:
> > 
> > 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"?
> 
> Definitely possible.  The last similar change happened in December and
> took until March until I ran out of stupid regressions from it.  Most
> likely there are still some I just haven't found yet.
> 
> The question is when to draw the line and say "This is useful as-is for
> a sufficient number of users."  I don't have a good answer to it.  I
> certainly expect more changes in the future, including format changes.
> And if we wait for them all to happen, it won't get merged this decade.

Why not merge it and mark it experimental then ? In fact, this is about
what you're looking for : reduced merge hassle and more testers.

Willy

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