From: kernel test robot <lkp@intel.com>
To: Tom Haynes <loghyr@hammerspace.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
0day robot <lkp@intel.com>,
Mike Snitzer <snitzer@hammerspace.com>
Subject: fs/nfs/nfs4proc.c:231:2: error: expected expression
Date: Fri, 14 Aug 2026 14:06:40 +0200 [thread overview]
Message-ID: <202608141400.RkKLVEMl-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Mike-Snitzer/nfs4-2-add-nfs4_2-x-to-generate-the-UNCACHEABLE_FILE_DATA-attribute/20260809-013525
head: d4e3d375fc17be88b916893f8c10abf763e51718
commit: 05a7e931533f15c5e8a56b30cd59cd2aafc5c717 nfs4.2: add UNCACHEABLE_FILE_DATA attribute support
date: 6 days ago
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260814/202608141400.RkKLVEMl-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260814/202608141400.RkKLVEMl-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/202608141400.RkKLVEMl-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/nfs/nfs4proc.c:231:2: error: expected expression
231 | | FATTR4_WORD2_UNCACHEABLE_FILE_DATA
| ^
1 error generated.
vim +231 fs/nfs/nfs4proc.c
207
208 /*
209 * This is our standard bitmap for GETATTR requests.
210 */
211 const u32 nfs4_fattr_bitmap[3] = {
212 FATTR4_WORD0_TYPE
213 | FATTR4_WORD0_CHANGE
214 | FATTR4_WORD0_SIZE
215 | FATTR4_WORD0_FSID
216 | FATTR4_WORD0_FILEID,
217 FATTR4_WORD1_MODE
218 | FATTR4_WORD1_NUMLINKS
219 | FATTR4_WORD1_OWNER
220 | FATTR4_WORD1_OWNER_GROUP
221 | FATTR4_WORD1_RAWDEV
222 | FATTR4_WORD1_SPACE_USED
223 | FATTR4_WORD1_TIME_ACCESS
224 | FATTR4_WORD1_TIME_CREATE
225 | FATTR4_WORD1_TIME_METADATA
226 | FATTR4_WORD1_TIME_MODIFY
227 | FATTR4_WORD1_MOUNTED_ON_FILEID,
228 #ifdef CONFIG_NFS_V4_SECURITY_LABEL
229 FATTR4_WORD2_SECURITY_LABEL
230 #endif
> 231 | FATTR4_WORD2_UNCACHEABLE_FILE_DATA
232 };
233
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-14 12:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202608141400.RkKLVEMl-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=loghyr@hammerspace.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=snitzer@hammerspace.com \
/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