All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: LastAvengers <lastavengers@outlook.com>, Jan Kara <jack@suse.com>,
	Andreas Dilger <adilger.kernel@dilger.ca>,
	linux-ext4@vger.kernel.org
Subject: Re: xattr index for hurd
Date: Mon, 1 Aug 2016 09:03:35 -0400	[thread overview]
Message-ID: <20160801130335.GG12853@thunk.org> (raw)
In-Reply-To: <20160801060453.GA32095@infradead.org>

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

      reply	other threads:[~2016-08-01 13:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a3ef36c5-cd3b-5fc2-e9fc-eb7e823f0510@outlook.com>
     [not found] ` <BLU175-W270CF93954CBCB94CA36CC9360@phx.gbl>
2016-08-01  3:42   ` xattr index for hurd Theodore Ts'o
2016-08-01  6:04     ` Christoph Hellwig
2016-08-01 13:03       ` Theodore Ts'o [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160801130335.GG12853@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger.kernel@dilger.ca \
    --cc=hch@infradead.org \
    --cc=jack@suse.com \
    --cc=lastavengers@outlook.com \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.