mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeffrey E Altman <jaltman@auristor.com>
To: "David Howells (dhowells@redhat.com)" <dhowells@redhat.com>,
	linux-afs@lists.infradead.org
Cc: Gaja Sophie Peters <gaja.peters@math.uni-hamburg.de>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] AFS metadata xattr fixes
Date: Thu, 11 Mar 2021 09:54:47 -0500	[thread overview]
Message-ID: <08de868e-d207-8980-1da4-da79eda07560@auristor.com> (raw)
In-Reply-To: <161547181530.1868820.12933722592029066752.stgit@warthog.procyon.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 826 bytes --]

On 3/11/2021 9:10 AM, David Howells (dhowells@redhat.com) wrote:
> I wonder if it's better to just hide all the afs.* xattrs from listxattr().
> It would probably be even better to not use xattrs for this, but I'm not
> sure what I would use instead.

I believe that all of the "afs.*" xattrs should be hidden from 
listxattr().  Any "afs.*" xattr that is read from an afs inode can be 
copied to another filesystem and stored.  Attempts to set these values 
in an afs volume will fail.

The use of xattrs is intended to be an alternative to the IBM/OpenAFS 
pioctls which are accessed by processes such as "fs", "aklog", "tokens", 
etc which would know the names of the xattrs and how to use them.   Such 
tools would not require listxattr() to find them.

Thanks for the consideration.

Jeffrey Altman



[-- Attachment #1.2: jaltman.vcf --]
[-- Type: text/x-vcard, Size: 283 bytes --]

begin:vcard
fn:Jeffrey Altman
n:Altman;Jeffrey
org:AuriStor, Inc.
adr:;;255 W 94TH ST STE 6B;New York;NY;10025-6985;United States
email;internet:jaltman@auristor.com
title:CEO
tel;work:+1-212-769-9018
url:https://www.linkedin.com/in/jeffreyaltman/
version:2.1
end:vcard


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4033 bytes --]

      parent reply	other threads:[~2021-03-11 15:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 14:10 David Howells
2021-03-11 14:10 ` [PATCH 1/2] afs: Fix accessing YFS xattrs on a non-YFS server David Howells
2021-03-11 18:26   ` Marc Dionne
2021-03-11 14:10 ` [PATCH 2/2] afs: Fix afs_listxattr() to not list afs ACL special xattrs David Howells
2021-03-11 18:59   ` Marc Dionne
2021-03-11 14:54 ` Jeffrey E Altman [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=08de868e-d207-8980-1da4-da79eda07560@auristor.com \
    --to=jaltman@auristor.com \
    --cc=dhowells@redhat.com \
    --cc=gaja.peters@math.uni-hamburg.de \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®