From: kernel test robot <lkp@intel.com>
To: rick.macklem@gmail.com, linux-nfs@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Rick Macklem <rmacklem@uoguelph.ca>
Subject: Re: [PATCH v1 5/7] Make nfs4_server_supports_acls() global
Date: Sat, 10 Jan 2026 07:50:45 +0800 [thread overview]
Message-ID: <202601100751.PT89Ryd4-lkp@intel.com> (raw)
In-Reply-To: <20260102232934.1560-6-rick.macklem@gmail.com>
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on trondmy-nfs/linux-next]
[also build test ERROR on linus/master v6.19-rc4 next-20260109]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/rick-macklem-gmail-com/Add-entries-to-the-predefined-client-operations-enum/20260103-073239
base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
patch link: https://lore.kernel.org/r/20260102232934.1560-6-rick.macklem%40gmail.com
patch subject: [PATCH v1 5/7] Make nfs4_server_supports_acls() global
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20260110/202601100751.PT89Ryd4-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260110/202601100751.PT89Ryd4-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202601100751.PT89Ryd4-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/nfs/nfs4proc.c:6083:36: error: use of undeclared identifier 'FATTR4_WORD2_POSIX_DEFAULT_ACL'
6083 | return server->attr_bitmask[2] & FATTR4_WORD2_POSIX_DEFAULT_ACL;
| ^
>> fs/nfs/nfs4proc.c:6085:36: error: use of undeclared identifier 'FATTR4_WORD2_POSIX_ACCESS_ACL'
6085 | return server->attr_bitmask[2] & FATTR4_WORD2_POSIX_ACCESS_ACL;
| ^
2 errors generated.
vim +/FATTR4_WORD2_POSIX_DEFAULT_ACL +6083 fs/nfs/nfs4proc.c
6071
6072 bool nfs4_server_supports_acls(const struct nfs_server *server,
6073 enum nfs4_acl_type type)
6074 {
6075 switch (type) {
6076 default:
6077 return server->attr_bitmask[0] & FATTR4_WORD0_ACL;
6078 case NFS4ACL_DACL:
6079 return server->attr_bitmask[1] & FATTR4_WORD1_DACL;
6080 case NFS4ACL_SACL:
6081 return server->attr_bitmask[1] & FATTR4_WORD1_SACL;
6082 case NFS4ACL_POSIXDEFAULT:
> 6083 return server->attr_bitmask[2] & FATTR4_WORD2_POSIX_DEFAULT_ACL;
6084 case NFS4ACL_POSIXACCESS:
> 6085 return server->attr_bitmask[2] & FATTR4_WORD2_POSIX_ACCESS_ACL;
6086 }
6087 }
6088
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-01-09 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260102232934.1560-6-rick.macklem@gmail.com>
2026-01-03 14:37 ` [PATCH v1 5/7] Make nfs4_server_supports_acls() global kernel test robot
2026-01-03 16:04 ` Rick Macklem
2026-01-09 23:50 ` kernel test robot [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=202601100751.PT89Ryd4-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-nfs@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rick.macklem@gmail.com \
--cc=rmacklem@uoguelph.ca \
/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