From: kernel test robot <lkp@intel.com>
To: Chuck Lever <chuck.lever@oracle.com>, linux-nfs@vger.kernel.org
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH v2 3/4] SUNRPC: Move client-side disconnect injection
Date: Wed, 11 Aug 2021 12:08:20 +0800 [thread overview]
Message-ID: <202108111211.nyVVUUXf-lkp@intel.com> (raw)
In-Reply-To: <162862957325.263874.15090477735404502036.stgit@klimt.1015granger.net>
[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]
Hi Chuck,
I love your patch! Yet something to improve:
[auto build test ERROR on nfs/linux-next]
[also build test ERROR on linus/master v5.14-rc5 next-20210810]
[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]
url: https://github.com/0day-ci/linux/commits/Chuck-Lever/SunRPC-fault-injection/20210811-050828
base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
config: openrisc-randconfig-r025-20210811 (attached as .config)
compiler: or1k-linux-gcc (GCC) 10.3.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://github.com/0day-ci/linux/commit/f1aa75010640cf376cac8baca8d42fda71472772
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Chuck-Lever/SunRPC-fault-injection/20210811-050828
git checkout f1aa75010640cf376cac8baca8d42fda71472772
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross O=build_dir ARCH=openrisc SHELL=/bin/bash
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 >>):
or1k-linux-ld: net/sunrpc/xprt.o: in function `xprt_inject_disconnect':
xprt.c:(.text+0x2dd4): undefined reference to `fail_sunrpc'
>> or1k-linux-ld: xprt.c:(.text+0x2dd8): undefined reference to `fail_sunrpc'
or1k-linux-ld: net/sunrpc/xprt.o: in function `xprt_end_transmit':
xprt.c:(.text+0x7b20): undefined reference to `fail_sunrpc'
or1k-linux-ld: xprt.c:(.text+0x7b28): undefined reference to `fail_sunrpc'
or1k-linux-ld: net/sunrpc/svc.o: in function `svc_process':
svc.c:(.text+0x4f64): undefined reference to `fail_sunrpc'
or1k-linux-ld: net/sunrpc/svc.o:svc.c:(.text+0x4f80): more undefined references to `fail_sunrpc' follow
---
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: 33867 bytes --]
next prev parent reply other threads:[~2021-08-11 4:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 21:05 [PATCH v2 0/4] SunRPC fault injection Chuck Lever
2021-08-10 21:06 ` [PATCH v2 1/4] SUNRPC: Add a /sys/kernel/debug/fail_sunrpc/ directory Chuck Lever
2021-08-10 23:31 ` kernel test robot
2021-08-11 6:26 ` kernel test robot
2021-08-10 21:06 ` [PATCH v2 2/4] SUNRPC: Server-side disconnect injection Chuck Lever
2021-08-11 10:39 ` kernel test robot
2021-08-10 21:06 ` [PATCH v2 3/4] SUNRPC: Move client-side " Chuck Lever
2021-08-11 4:08 ` kernel test robot [this message]
2021-08-10 21:06 ` [PATCH v2 4/4] SUNRPC: Add documentation for the fail_sunrpc/ directory Chuck Lever
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=202108111211.nyVVUUXf-lkp@intel.com \
--to=lkp@intel.com \
--cc=chuck.lever@oracle.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-nfs@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