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 v1 2/4] SUNRPC: Server-side disconnect injection
Date: Tue, 10 Aug 2021 07:18:51 +0800 [thread overview]
Message-ID: <202108100713.EvrdqNpe-lkp@intel.com> (raw)
In-Reply-To: <162853257078.4752.13164987567936683026.stgit@klimt.1015granger.net>
[-- Attachment #1: Type: text/plain, Size: 2370 bytes --]
Hi Chuck,
I love your patch! Yet something to improve:
[auto build test ERROR on nfs/linux-next]
[also build test ERROR on nfsd/nfsd-next linus/master v5.14-rc5 next-20210809]
[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/20210810-021150
base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
config: i386-randconfig-r033-20210809 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/561bf84b4d936dc5ae88b55b133def1b7e50d263
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Chuck-Lever/SunRPC-fault-injection/20210810-021150
git checkout 561bf84b4d936dc5ae88b55b133def1b7e50d263
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash net/
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 net/sunrpc/svc.c:34:
>> net/sunrpc/fail.h:12:20: error: field 'attr' has incomplete type
12 | struct fault_attr attr;
| ^~~~
net/sunrpc/svc.c: In function 'svc_process':
>> net/sunrpc/svc.c:1509:6: error: implicit declaration of function 'should_fail'; did you mean 'should_failslab'? [-Werror=implicit-function-declaration]
1509 | should_fail(&fail_sunrpc.attr, 1))
| ^~~~~~~~~~~
| should_failslab
cc1: some warnings being treated as errors
vim +/attr +12 net/sunrpc/fail.h
f6324480d4b27a2 Chuck Lever 2021-08-09 10
f6324480d4b27a2 Chuck Lever 2021-08-09 11 struct fail_sunrpc_attr {
f6324480d4b27a2 Chuck Lever 2021-08-09 @12 struct fault_attr attr;
561bf84b4d936dc Chuck Lever 2021-08-09 13
561bf84b4d936dc Chuck Lever 2021-08-09 14 bool ignore_server_disconnect;
f6324480d4b27a2 Chuck Lever 2021-08-09 15 };
f6324480d4b27a2 Chuck Lever 2021-08-09 16
---
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: 36621 bytes --]
next prev parent reply other threads:[~2021-08-09 23:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 18:09 [PATCH v1 0/4] SunRPC fault injection Chuck Lever
2021-08-09 18:09 ` [PATCH v1 1/4] SUNRPC: Add a /sys/kernel/debug/fail_sunrpc/ directory Chuck Lever
2021-08-09 21:25 ` kernel test robot
2021-08-09 18:09 ` [PATCH v1 2/4] SUNRPC: Server-side disconnect injection Chuck Lever
2021-08-09 21:16 ` kernel test robot
2021-08-09 23:18 ` kernel test robot [this message]
2021-08-09 18:09 ` [PATCH v1 3/4] SUNRPC: Move client-side " Chuck Lever
2021-08-09 18:09 ` [PATCH v1 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=202108100713.EvrdqNpe-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