From: kernel test robot <lkp@intel.com>
To: NeilBrown <neilb@suse.de>,
Chuck Lever III <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH nfsd-next] SQUASH sunrpc: allow svc threads to fail initialisation cleanly
Date: Mon, 16 Sep 2024 10:27:53 +0800 [thread overview]
Message-ID: <202409161033.eurajfZc-lkp@intel.com> (raw)
In-Reply-To: <172644394073.17050.16376953609629336068@noble.neil.brown.name>
Hi NeilBrown,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20240913]
[cannot apply to trondmy-nfs/linux-next v6.11 v6.11-rc7 v6.11-rc6 linus/master v6.11]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/NeilBrown/SQUASH-sunrpc-allow-svc-threads-to-fail-initialisation-cleanly/20240916-074739
base: next-20240913
patch link: https://lore.kernel.org/r/172644394073.17050.16376953609629336068%40noble.neil.brown.name
patch subject: [PATCH nfsd-next] SQUASH sunrpc: allow svc threads to fail initialisation cleanly
config: x86_64-rhel-8.3-bpf (https://download.01.org/0day-ci/archive/20240916/202409161033.eurajfZc-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/20240916/202409161033.eurajfZc-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/202409161033.eurajfZc-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/sunrpc/svcsock.h:13,
from include/linux/sunrpc/bc_xprt.h:16,
from net/sunrpc/clnt.c:40:
include/linux/sunrpc/svc.h: In function 'svc_thread_init_status':
>> include/linux/sunrpc/svc.h:333:9: error: implicit declaration of function 'smb_mb'; did you mean 'smp_mb'? [-Werror=implicit-function-declaration]
333 | smb_mb();
| ^~~~~~
| smp_mb
cc1: some warnings being treated as errors
vim +333 include/linux/sunrpc/svc.h
313
314 /**
315 * svc_thread_init_status - report whether thread has initialised successfully
316 * @rqstp: the thread in question
317 * @err: errno code
318 *
319 * After performing any initialisation that could fail, and before starting
320 * normal work, each sunrpc svc_thread must call svc_thread_init_status()
321 * with an appropriate error, or zero.
322 *
323 * If zero is passed, the thread is ready and must continue until
324 * svc_thread_should_stop() returns true. If a non-zero error is passed
325 * the call will not return - the thread will exit.
326 */
327 static inline void svc_thread_init_status(struct svc_rqst *rqstp, int err)
328 {
329 rqstp->rq_err = err;
330 /* memory barrier ensures assignment to error above is visible before
331 * waitqueue_active() test below completes.
332 */
> 333 smb_mb();
334 wake_up_var(&rqstp->rq_err);
335 if (err)
336 kthread_exit(1);
337 }
338
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-16 2:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 23:45 [PATCH nfsd-next] SQUASH sunrpc: allow svc threads to fail initialisation cleanly NeilBrown
2024-09-16 0:24 ` Jeff Layton
2024-09-16 2:27 ` kernel test robot [this message]
2024-09-16 2:27 ` kernel test robot
2024-09-16 3:50 ` 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=202409161033.eurajfZc-lkp@intel.com \
--to=lkp@intel.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=neilb@suse.de \
--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.