linux-kernel - Re: reiser4 for 2.6.33?

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:	Wed, 18 Nov 2009 11:12:12 -0800 (PST)
From:	Christian Kujau <lists@...dbynature.de>
To:	Edward Shishkin <edward.shishkin@...il.com>
cc:	reiserfs-devel@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>, akpm@...ux-foundation.org
Subject: Re: reiser4 for 2.6.33?

On Wed, 18 Nov 2009 at 14:50, Edward Shishkin wrote:
> (a) plugin design document;
> (b) full description of what is going on in respond to memory
>    pressure notifications;
> 
> The (a) is not yet ready and I don't have a time to explain
> personally to everyone why the plugin stuff is not crappy.

Is this still a must-have? I.e. are there still strong objections against 
the plugin design? And even if so, most of this happens in fs/reiser4 
anyway I suppose, so the "evil" plugins are well contained :)

As for (b), can't this be documented at a later point as well? 

What about the technical issues, mentioned in the latest TODO list[0] 
earlier this year? Are there any real show-stoppers left?
Andrew (Cc'ed) had this in -mm for a longer time now, maybe he can
comment (once again) what's left to do from his POV?

Thanks,
Christian.

[0] http://marc.info/?l=reiserfs-devel&m=124069989217533&w=2
-- 
BOFH excuse #323:

Your processor has processed too many instructions.  Turn it off immediately, do not type any commands!!
--
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/