All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH RFC v9 2/2] nfsd: Initial implementation of NFSv4 Courteous Server
Date: Tue, 11 Jan 2022 04:52:12 +0800	[thread overview]
Message-ID: <202201110428.jF9JKms7-lkp@intel.com> (raw)
In-Reply-To: <1641840653-23059-3-git-send-email-dai.ngo@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 3794 bytes --]

Hi Dai,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on linus/master]
[also build test WARNING on v5.16 next-20220110]
[cannot apply to cel-2.6/for-next jlayton/linux-next]
[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/Dai-Ngo/nfsd-Initial-implementation-of-NFSv4-Courteous-Server/20220111-025146
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git df0cc57e057f18e44dac8e6c18aba47ab53202f9
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20220111/202201110428.jF9JKms7-lkp(a)intel.com/config)
compiler: m68k-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://github.com/0day-ci/linux/commit/9d727ed1cc3cca2c8f60573a24cfcddb9780c5e7
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Dai-Ngo/nfsd-Initial-implementation-of-NFSv4-Courteous-Server/20220111-025146
        git checkout 9d727ed1cc3cca2c8f60573a24cfcddb9780c5e7
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=m68k SHELL=/bin/bash fs/nfsd/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> fs/nfsd/nfs4state.c:167:1: warning: no previous prototype for 'renew_client_locked' [-Wmissing-prototypes]
     167 | renew_client_locked(struct nfs4_client *clp)
         | ^~~~~~~~~~~~~~~~~~~


vim +/renew_client_locked +167 fs/nfsd/nfs4state.c

221a68766973d7 J. Bruce Fields 2013-04-01  162  
9d727ed1cc3cca Dai Ngo         2022-01-10  163  /* must be called under the client_lock
221a68766973d7 J. Bruce Fields 2013-04-01  164  static inline void
9d727ed1cc3cca Dai Ngo         2022-01-10  165  */
9d727ed1cc3cca Dai Ngo         2022-01-10  166  void
221a68766973d7 J. Bruce Fields 2013-04-01 @167  renew_client_locked(struct nfs4_client *clp)
221a68766973d7 J. Bruce Fields 2013-04-01  168  {
221a68766973d7 J. Bruce Fields 2013-04-01  169  	struct nfsd_net *nn = net_generic(clp->net, nfsd_net_id);
221a68766973d7 J. Bruce Fields 2013-04-01  170  
221a68766973d7 J. Bruce Fields 2013-04-01  171  	if (is_client_expired(clp)) {
221a68766973d7 J. Bruce Fields 2013-04-01  172  		WARN_ON(1);
221a68766973d7 J. Bruce Fields 2013-04-01  173  		printk("%s: client (clientid %08x/%08x) already expired\n",
221a68766973d7 J. Bruce Fields 2013-04-01  174  			__func__,
221a68766973d7 J. Bruce Fields 2013-04-01  175  			clp->cl_clientid.cl_boot,
221a68766973d7 J. Bruce Fields 2013-04-01  176  			clp->cl_clientid.cl_id);
221a68766973d7 J. Bruce Fields 2013-04-01  177  		return;
221a68766973d7 J. Bruce Fields 2013-04-01  178  	}
221a68766973d7 J. Bruce Fields 2013-04-01  179  
221a68766973d7 J. Bruce Fields 2013-04-01  180  	list_move_tail(&clp->cl_lru, &nn->client_lru);
20b7d86f29d39e Arnd Bergmann   2019-11-04  181  	clp->cl_time = ktime_get_boottime_seconds();
9d727ed1cc3cca Dai Ngo         2022-01-10  182  	clear_bit(NFSD4_COURTESY_CLIENT, &clp->cl_flags);
221a68766973d7 J. Bruce Fields 2013-04-01  183  }
9d727ed1cc3cca Dai Ngo         2022-01-10  184  EXPORT_SYMBOL_GPL(renew_client_locked);
221a68766973d7 J. Bruce Fields 2013-04-01  185  

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

  reply	other threads:[~2022-01-10 20:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 18:50 [PATCH RFC v9 0/2] nfsd: Initial implementation of NFSv4 Courteous Server Dai Ngo
2022-01-10 18:50 ` [PATCH RFC v9 1/2] fs/lock: add new callback, lm_expire_lock, to lock_manager_operations Dai Ngo
2022-01-10 18:50 ` [PATCH RFC v9 2/2] nfsd: Initial implementation of NFSv4 Courteous Server Dai Ngo
2022-01-10 20:52   ` kernel test robot [this message]
2022-01-10 23:17   ` Chuck Lever III
2022-01-11  1:03     ` dai.ngo
2022-01-11 15:49       ` Chuck Lever III
2022-01-12 18:53         ` Bruce Fields
2022-01-12 18:56           ` dai.ngo
2022-01-12 19:40   ` J. Bruce Fields
2022-01-13  8:51     ` dai.ngo
2022-01-13 15:42       ` J. Bruce Fields
2022-01-13 19:51         ` dai.ngo
2022-01-12 19:52   ` J. Bruce Fields
2022-01-10 19:03 ` [PATCH RFC v9 0/2] " Chuck Lever III
2022-01-12 18:59 ` J. Bruce Fields
2022-01-12 19:05   ` dai.ngo
2022-01-12 19:21     ` J. Bruce Fields
2022-01-12 19:31       ` dai.ngo
2022-01-12 19:42         ` J. Bruce Fields
2022-01-12 20:34           ` dai.ngo
2022-01-12 20:39             ` J. Bruce Fields
  -- strict thread matches above, loose matches on Subject: below --
2022-01-10 18:40 Dai Ngo
2022-01-10 18:40 ` [PATCH RFC v9 2/2] " Dai Ngo

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=202201110428.jF9JKms7-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.