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:	Tue, 18 Jul 2006 18:38:10 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Hans Reiser <reiser@...esys.com>
cc:	Jeff Mahoney <jeffm@...e.com>, 7eggert@....de,
	Eric Dumazet <dada1@...mosbay.com>,
	ReiserFS List <reiserfs-list@...esys.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>
Subject: Re: [PATCH] reiserfs: fix handling of device names with /'s in them

>
>Try v4.
>
>> My original xattr
>> implementation added another item type, but oh -- wait -- it turns out
>> that the file system isn't quite as extensible as claimed.. or, well, AT
>> ALL. Adding another item results in an incompatible file system change
>> that when mounted on another system, will panic the node. That's
>> friendly! There's not even any way to identify which items are in use on
>> a particular file system to issue a warning/error on mount. Outstanding
>> job "architecting" there.
>
>Well, if you had an obsessive desire to not use V4, you could fix this
>in V3 instead.
>
>Might be easier to use V4...
>
>> Users
>> wanted ACLs and xattrs on reiser3, but you said, "wait for v4, it'll be
>> out soon, and it'll have them." That was 4 years ago. Reiser4 still
>> isn't completely stable 

My word here is done:

While reiserfs3 actually got ACLs, xattrs and quota support by now, reiser4
still lacks them. Something must be very wrong to suggest V4; at least when it
comes to these three things.


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ