linux-ext4 - Re: xattr index for hurd

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:	Mon, 1 Aug 2016 09:03:35 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	LastAvengers <lastavengers@...look.com>, Jan Kara <jack@...e.com>,
	Andreas Dilger <adilger.kernel@...ger.ca>,
	linux-ext4@...r.kernel.org
Subject: Re: xattr index for hurd

On Sun, Jul 31, 2016 at 11:04:53PM -0700, Christoph Hellwig wrote:
> Note thast _iff_ you ever want to expose the hurd xattrs under Linux
> (or in fact at all - gnu.* is only fine for purely internal usage)
> please use the system namespace.  We really shouldn't expose more than
> the existing namespaces to userspace.

Hmm, good point.  If you're not going to expose it at all, then the
system namespace works fine.  One potential concern with that plan is
that we don't have a way of coordinating *use* of the system namespace
across Linux and Hurd, though.  We may need to come up with some kind
of convention for that purpose.  Note that for space reasons, there's
no need to make the ascii string used in the system namespace to be
long.  So something like GNUt and GNUa for the translator and author
fields is better from the reducing the space used for the xattrs
(which is important if you are using a 256 byte inode and want to keep
the xattr inside the inode table).

							- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html