nfs4 v5.1-rc1, listxattr succeeded but getxattr

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

To: Trond Myklebust <trond.myklebust@xxxxxxxxxxxxxxx>, Anna Schumaker <anna.schumaker@xxxxxxxxxx>
Subject: nfs4 v5.1-rc1, listxattr succeeded but getxattr
From: "J. R. Okajima" <hooanon05g@xxxxxxxxx>
Date: Mon, 25 Mar 2019 14:08:38 +0900
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, linux-nfs@xxxxxxxxxxxxxxx

On linux-v5.1-rc1, NFSv4 listxattr(2) returns "system.nfs4_acl".  It is
OK, but getxattr(2) returns EOPNOTSUPP.  Is it an expected behaviour?

On v5.0, NFSv4 getxattr(2) didn't return the error.


J. R. Okajima

Prev by Date: Re: KASAN: use-after-free Read in path_lookupat
Next by Date: Re: [QUESTION] Long read latencies on mixed rw buffered IO
Previous by thread: [patch] fanotify.7, fanotify_init.2, fanotify_mark.2: Document FAN_REPORT_FID and directory modification events
Next by thread: Re: [QUESTION] Long read latencies on mixed rw buffered IO
Index(es):
- Date
- Thread

[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