Re: [PATCH 0/2] AFS metadata xattr fixes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 3/11/2021 9:10 AM, David Howells (dhowells@xxxxxxxxxx) 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@xxxxxxxxxxxx
title:CEO
tel;work:+1-212-769-9018
url:https://www.linkedin.com/in/jeffreyaltman/
version:2.1
end:vcard

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux