linux-kernel - Re: Question about Reiser4

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:	Wed, 25 Apr 2007 18:35:03 +0400
From:	Edward Shishkin <edward@...esys.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	"Vladimir V. Saveliev" <vs@...esys.com>,
	Alex Zarochentsev <zam@...esys.com>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Eric Hopper <hopper@...ifarious.org>, Lex Lyamin <flx@....ru>,
	William Heimbigner <icxcnika@....tar.cc>,
	Rik van Riel <riel@...hat.com>,
	Xu CanHao <xucanhao@...il.com>
Subject: Re: Question about Reiser4

Andi Kleen wrote:

>>Because there are unaddressed items in this todo list:
>>http://pub.namesys.com/Reiser4/ToDo
>>The main issues here are xattrs and support for blocksize != pagesize.
>>    
>>
>
>I would consider both to be optional. We have various file systems
>in tree that don't support either (e.g. JFS only supports 4K blocks
>and OCFS2 doesn't support xattr) They shouldn't block merging.
>
>  
>

xattrs also were considered as some guarantee of vendor support.
If possible, then we'll address it as low-priority issue.
Maybe somebody will help.. (xattrs support should go as incremental
update of FPL-subversion for reiser4 kernel module and reiser4progs).

>>2. Who will maintain this?
>>
>>Currently there are two namesys employees working mostly on
>>enthusiasm. Divide them into 2 file systems, plus many people who
>>really help with fixing problems.
>>    
>>
>
>Merging will probably be a peak of work for the necessary changes,
>then hopefully the work will be less once you're in tree because
>you don't need to track mainline anymore
>(assuming not to many bugs come in from users) 
>
>-Andi
>  
>

Hope we survive this, at least such peaks is not something new in
our practice.

Well, gentlemen, so we'll address other items (except #26, 27) and
resume this discussion.

Thanks,
Edward.

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