From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jlayton:dir-deleg-clnt 10/11] fs/nfs/nfs4xdr.c:2042:33: error: 'NOTIFY4_REMOVE_ENTRY' undeclared
Date: Fri, 30 May 2025 20:20:58 +0800 [thread overview]
Message-ID: <202505302031.wHUsevsF-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git dir-deleg-clnt
head: ea15531aa828dc21ac17cc091ec2a178ec621a34
commit: 1168a584087801319341982a4de5d46b5c79e9c6 [10/11] nfs: allow client to request NOTIFY4_REMOVE_ENTRY
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20250530/202505302031.wHUsevsF-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250530/202505302031.wHUsevsF-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/202505302031.wHUsevsF-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/bits.h:6,
from include/linux/ratelimit_types.h:5,
from include/linux/printk.h:9,
from include/asm-generic/bug.h:22,
from arch/x86/include/asm/bug.h:103,
from arch/x86/include/asm/alternative.h:9,
from arch/x86/include/asm/segment.h:6,
from arch/x86/include/asm/ptrace.h:5,
from arch/x86/include/asm/math_emu.h:5,
from arch/x86/include/asm/processor.h:13,
from arch/x86/include/asm/timex.h:5,
from include/linux/timex.h:67,
from include/linux/time32.h:13,
from include/linux/time.h:60,
from fs/nfs/nfs4xdr.c:39:
fs/nfs/nfs4xdr.c: In function 'encode_get_dir_delegation':
>> fs/nfs/nfs4xdr.c:2042:33: error: 'NOTIFY4_REMOVE_ENTRY' undeclared (first use in this function)
2042 | u32 notifybm[1] = { BIT(NOTIFY4_REMOVE_ENTRY) };
| ^~~~~~~~~~~~~~~~~~~~
include/vdso/bits.h:7:44: note: in definition of macro 'BIT'
7 | #define BIT(nr) (UL(1) << (nr))
| ^~
fs/nfs/nfs4xdr.c:2042:33: note: each undeclared identifier is reported only once for each function it appears in
2042 | u32 notifybm[1] = { BIT(NOTIFY4_REMOVE_ENTRY) };
| ^~~~~~~~~~~~~~~~~~~~
include/vdso/bits.h:7:44: note: in definition of macro 'BIT'
7 | #define BIT(nr) (UL(1) << (nr))
| ^~
vim +/NOTIFY4_REMOVE_ENTRY +2042 fs/nfs/nfs4xdr.c
2035
2036 #ifdef CONFIG_NFS_V4_1
2037 static void
2038 encode_get_dir_delegation(struct xdr_stream *xdr, struct compound_hdr *hdr)
2039 {
2040 __be32 *p;
2041 struct timespec64 ts = {};
> 2042 u32 notifybm[1] = { BIT(NOTIFY4_REMOVE_ENTRY) };
2043 u32 zerobm[1] = {};
2044
2045 encode_op_hdr(xdr, OP_GET_DIR_DELEGATION, decode_get_dir_delegation_maxsz, hdr);
2046
2047 /* We can't handle CB_RECALLABLE_OBJ_AVAIL yet */
2048 xdr_stream_encode_bool(xdr, false);
2049
2050 xdr_encode_bitmap4(xdr, notifybm, ARRAY_SIZE(notifybm));
2051
2052 /* Request no attribute updates */
2053 p = reserve_space(xdr, 12 + 12);
2054 p = xdr_encode_nfstime4(p, &ts);
2055 xdr_encode_nfstime4(p, &ts);
2056
2057 xdr_encode_bitmap4(xdr, zerobm, ARRAY_SIZE(zerobm));
2058 xdr_encode_bitmap4(xdr, zerobm, ARRAY_SIZE(zerobm));
2059 }
2060
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-30 12:21 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=202505302031.wHUsevsF-lkp@intel.com \
--to=lkp@intel.com \
--cc=jlayton@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.