lkml.org 
[lkml]   [2021]   [Mar]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 0/2] AFS metadata xattr fixes
From
Date
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


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

[unhandled content-type:application/pkcs7-signature]
\
 
 \ /
  Last update: 2021-03-11 16:01    [W:0.165 / U:0.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site