From: kernel test robot <lkp@intel.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [cel:topic-xdr-tracepoints 50/169] include/trace/../../fs/lockd/xdrtrace.h:35:19: error: 'NLM_DEADLCK' undeclared here (not in a function)
Date: Mon, 22 Nov 2021 23:23:32 +0800 [thread overview]
Message-ID: <202111222326.1cDRZQKB-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3987 bytes --]
tree: git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux topic-xdr-tracepoints
head: 07f44f67cedcceb30d1fc98899a509d7da3827d1
commit: ccff37ef1fdeb303eab48ff46b0df0e80867c4f0 [50/169] lockd: Infrastructure for lockd server-side XDR tracepoints
config: openrisc-randconfig-r011-20211122 (attached as .config)
compiler: or1k-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git/commit/?id=ccff37ef1fdeb303eab48ff46b0df0e80867c4f0
git remote add cel git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux
git fetch --no-tags cel topic-xdr-tracepoints
git checkout ccff37ef1fdeb303eab48ff46b0df0e80867c4f0
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=openrisc SHELL=/bin/bash fs/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from include/trace/define_trace.h:102,
from fs/lockd/xdrtrace.h:96,
from fs/lockd/xdrtrace.c:31:
>> include/trace/../../fs/lockd/xdrtrace.h:35:19: error: 'NLM_DEADLCK' undeclared here (not in a function)
35 | TRACE_DEFINE_ENUM(NLM_DEADLCK);
| ^~~~~~~~~~~
include/trace/trace_events.h:45:31: note: in definition of macro 'TRACE_DEFINE_ENUM'
45 | .eval_value = a \
| ^
>> include/trace/../../fs/lockd/xdrtrace.h:36:19: error: 'NLM_ROFS' undeclared here (not in a function)
36 | TRACE_DEFINE_ENUM(NLM_ROFS);
| ^~~~~~~~
include/trace/trace_events.h:45:31: note: in definition of macro 'TRACE_DEFINE_ENUM'
45 | .eval_value = a \
| ^
>> include/trace/../../fs/lockd/xdrtrace.h:37:19: error: 'NLM_STALE_FH' undeclared here (not in a function)
37 | TRACE_DEFINE_ENUM(NLM_STALE_FH);
| ^~~~~~~~~~~~
include/trace/trace_events.h:45:31: note: in definition of macro 'TRACE_DEFINE_ENUM'
45 | .eval_value = a \
| ^
>> include/trace/../../fs/lockd/xdrtrace.h:38:19: error: 'NLM_FBIG' undeclared here (not in a function)
38 | TRACE_DEFINE_ENUM(NLM_FBIG);
| ^~~~~~~~
include/trace/trace_events.h:45:31: note: in definition of macro 'TRACE_DEFINE_ENUM'
45 | .eval_value = a \
| ^
>> include/trace/../../fs/lockd/xdrtrace.h:39:19: error: 'NLM_FAILED' undeclared here (not in a function); did you mean 'MF_FAILED'?
39 | TRACE_DEFINE_ENUM(NLM_FAILED);
| ^~~~~~~~~~
include/trace/trace_events.h:45:31: note: in definition of macro 'TRACE_DEFINE_ENUM'
45 | .eval_value = a \
| ^
vim +/NLM_DEADLCK +35 include/trace/../../fs/lockd/xdrtrace.h
25
26 /**
27 ** Helpers
28 **/
29
30 TRACE_DEFINE_ENUM(NLM_LCK_GRANTED);
31 TRACE_DEFINE_ENUM(NLM_LCK_DENIED);
32 TRACE_DEFINE_ENUM(NLM_LCK_DENIED_NOLOCKS);
33 TRACE_DEFINE_ENUM(NLM_LCK_BLOCKED);
34 TRACE_DEFINE_ENUM(NLM_LCK_DENIED_GRACE_PERIOD);
> 35 TRACE_DEFINE_ENUM(NLM_DEADLCK);
> 36 TRACE_DEFINE_ENUM(NLM_ROFS);
> 37 TRACE_DEFINE_ENUM(NLM_STALE_FH);
> 38 TRACE_DEFINE_ENUM(NLM_FBIG);
> 39 TRACE_DEFINE_ENUM(NLM_FAILED);
40
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32345 bytes --]
reply other threads:[~2021-11-22 15:23 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=202111222326.1cDRZQKB-lkp@intel.com \
--to=lkp@intel.com \
--cc=chuck.lever@oracle.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
/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