linux-kernel - Re: metadata plugins (was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion)

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

Date:	Fri, 28 Jul 2006 10:02:04 -0400
From:	"Horst H. von Brand" <vonbrand@....utfsm.cl>
To:	Jeff Garzik <jeff@...zik.org>
cc:	Hans Reiser <reiser@...esys.com>, Andrew Morton <akpm@...l.org>,
	Theodore Tso <tytso@....edu>,
	LKML <linux-kernel@...r.kernel.org>,
	ReiserFS List <reiserfs-list@...esys.com>,
	Linus Torvalds <torvalds@...l.org>
Subject: Re: metadata plugins (was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion) 

Jeff Garzik <jeff@...zik.org> wrote:

[...]

> It is then simple to follow that train of logic:  why not make it easy
> to replace the directory algorithm [and associated metadata]?  or the
> file data space management algorithms?  or even the inode handling?
> why not allow customers to replace a stock algorithm with an exotic,
> site-specific one?

IMVHO, such experiments should/must be done in userspace. And AFAICS, they
can today.

Go wild, but leave the kernel alone.
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513
-
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/