Re: [PATCH] generic/062: more restrictive namespace for getfattr on cephfs

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



On Wed, 2019-07-24 at 18:49 +0300, Amir Goldstein wrote:
> On Wed, Jul 24, 2019 at 5:55 PM Jeff Layton <jlayton@xxxxxxxxxx> wrote:
> > cephfs exposes some information via virtual xattrs and their presence
> > causes this test to fail. When running on cephfs, only search for
> > specific xattr classes to ensure that we skip the ceph.* ones.
> > 
> 
> Probably too late to ask this question now anyway, but does ceph have
> a particular good reason to expose those virt xattr in listxattr?
> 
> I means its not xattrs that copy tools should try to copy and tools
> should know about them and can try to getxattr without the need
> to see them in listxattr.
> 
> I noticed this is the behavior of cifs w.r.t cifs. and smb3. virt xattr.
> 

Good question. I don't see the need for us to present these in listxattr
and stopping that may be the best solution here. Let me investigate that
approach.

Thanks,
-- 
Jeff Layton <jlayton@xxxxxxxxxx>




[Index of Archives]     [Linux Filesystems Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux