All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: NeilBrown <neilb@suse.de>, Chuck Lever <chuck.lever@oracle.com>,
	Jeff Layton <jlayton@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-nfs@vger.kernel.org,
	Olga Kornievskaia <kolga@netapp.com>,
	Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Subject: Re: [PATCH 1/6] nfsd: prepare for supporting admin-revocation of state
Date: Tue, 31 Oct 2023 11:17:31 +0800	[thread overview]
Message-ID: <202310311114.Ym5PyQ5Z-lkp@intel.com> (raw)
In-Reply-To: <20231027015613.26247-2-neilb@suse.de>

Hi NeilBrown,

kernel test robot noticed the following build errors:

[auto build test ERROR on linus/master]
[also build test ERROR on v6.6 next-20231030]
[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/nfsd-prepare-for-supporting-admin-revocation-of-state/20231027-095832
base:   linus/master
patch link:    https://lore.kernel.org/r/20231027015613.26247-2-neilb%40suse.de
patch subject: [PATCH 1/6] nfsd: prepare for supporting admin-revocation of state
config: mips-maltaup_xpa_defconfig (https://download.01.org/0day-ci/archive/20231031/202310311114.Ym5PyQ5Z-lkp@intel.com/config)
compiler: mipsel-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231031/202310311114.Ym5PyQ5Z-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/202310311114.Ym5PyQ5Z-lkp@intel.com/

All errors (new ones prefixed by >>):

   mipsel-linux-ld: fs/nfsd/nfsctl.o: in function `write_unlock_fs':
>> nfsctl.c:(.text+0x4cc): undefined reference to `nfsd4_revoke_states'

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2023-10-31  3:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27  1:45 [PATCH 0/6] support admin-revocation of v4 state NeilBrown
2023-10-27  1:45 ` [PATCH 1/6] nfsd: prepare for supporting admin-revocation of state NeilBrown
2023-10-31  2:45   ` kernel test robot
2023-10-31  3:17   ` kernel test robot [this message]
2023-10-27  1:45 ` [PATCH 2/6] nfsd: allow admin-revoked state to appear in /proc/fs/nfsd/clients/*/states NeilBrown
2023-10-27  1:45 ` [PATCH 3/6] nfsd: allow admin-revoked NFSv4.0 state to be freed NeilBrown
2023-10-31  0:13   ` kernel test robot
2023-10-27  1:45 ` [PATCH 4/6] nfsd: allow lock state ids to be revoked and then freed NeilBrown
2023-10-27  1:45 ` [PATCH 5/6] nfsd: allow open " NeilBrown
2023-10-27  1:45 ` [PATCH 6/6] nfsd: allow delegation " NeilBrown
     [not found] ` <ZTvaxWodP4rKFkrm@tissot.1015granger.net>
2023-10-27 22:10   ` [PATCH 0/6] support admin-revocation of v4 state NeilBrown
2023-10-27 23:34     ` Chuck Lever
  -- strict thread matches above, loose matches on Subject: below --
2023-11-01  0:57 [PATCH 0/6 v2] " NeilBrown
2023-11-01  0:57 ` [PATCH 1/6] nfsd: prepare for supporting admin-revocation of state NeilBrown
2023-11-01  2:14   ` Chuck Lever III
2023-11-01  2:49     ` NeilBrown
2023-11-02 10:46   ` Jeff Layton
2023-11-02 20:03     ` NeilBrown
2023-11-02 20:24       ` Jeff Layton
2023-11-02 20:29         ` Chuck Lever III
2023-11-03  1:08           ` NeilBrown
2023-11-03 14:34             ` Chuck Lever
2023-11-03 17:25             ` Jeff Layton
2023-11-02 11:25   ` Jeff Layton

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=202310311114.Ym5PyQ5Z-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Dai.Ngo@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=kolga@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tom@talpey.com \
    /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.