From: kernel test robot <lkp@intel.com>
To: Chuck Lever <cel@kernel.org>, NeilBrown <neil@brown.name>,
Jeff Layton <jlayton@kernel.org>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v5 1/7] NFSD: Extract revoke_one_stid() utility function
Date: Fri, 27 Mar 2026 19:13:12 +0800 [thread overview]
Message-ID: <202603271905.vZdE0ulk-lkp@intel.com> (raw)
In-Reply-To: <20260326-umount-kills-nfsv4-state-v5-1-d2ce071b3570@oracle.com>
Hi Chuck,
kernel test robot noticed the following build errors:
[auto build test ERROR on 65058e9e9b20619f920397f529072e853dd43811]
url: https://github.com/intel-lab-lkp/linux/commits/Chuck-Lever/NFSD-Extract-revoke_one_stid-utility-function/20260327-081757
base: 65058e9e9b20619f920397f529072e853dd43811
patch link: https://lore.kernel.org/r/20260326-umount-kills-nfsv4-state-v5-1-d2ce071b3570%40oracle.com
patch subject: [PATCH v5 1/7] NFSD: Extract revoke_one_stid() utility function
config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20260327/202603271905.vZdE0ulk-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260327/202603271905.vZdE0ulk-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/202603271905.vZdE0ulk-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/nfsd/nfs4state.c:1830:14: error: use of undeclared identifier 'state_lock'; did you mean 'task_lock'?
1830 | spin_lock(&state_lock);
| ^~~~~~~~~~
| task_lock
include/linux/sched/task.h:216:20: note: 'task_lock' declared here
216 | static inline void task_lock(struct task_struct *p)
| ^
fs/nfsd/nfs4state.c:1833:16: error: use of undeclared identifier 'state_lock'; did you mean 'task_lock'?
1833 | spin_unlock(&state_lock);
| ^~~~~~~~~~
| task_lock
include/linux/sched/task.h:216:20: note: 'task_lock' declared here
216 | static inline void task_lock(struct task_struct *p)
| ^
2 errors generated.
vim +1830 fs/nfsd/nfs4state.c
1805
1806 static void revoke_one_stid(struct nfs4_client *clp, struct nfs4_stid *stid)
1807 {
1808 struct nfs4_ol_stateid *stp;
1809 struct nfs4_delegation *dp;
1810
1811 switch (stid->sc_type) {
1812 case SC_TYPE_OPEN:
1813 stp = openlockstateid(stid);
1814 mutex_lock_nested(&stp->st_mutex, OPEN_STATEID_MUTEX);
1815 revoke_ol_stid(clp, stp);
1816 mutex_unlock(&stp->st_mutex);
1817 break;
1818 case SC_TYPE_LOCK:
1819 stp = openlockstateid(stid);
1820 mutex_lock_nested(&stp->st_mutex, LOCK_STATEID_MUTEX);
1821 revoke_ol_stid(clp, stp);
1822 mutex_unlock(&stp->st_mutex);
1823 break;
1824 case SC_TYPE_DELEG:
1825 /*
1826 * Extra reference guards against concurrent FREE_STATEID.
1827 */
1828 refcount_inc(&stid->sc_count);
1829 dp = delegstateid(stid);
> 1830 spin_lock(&state_lock);
1831 if (!unhash_delegation_locked(dp, SC_STATUS_ADMIN_REVOKED))
1832 dp = NULL;
1833 spin_unlock(&state_lock);
1834 if (dp)
1835 revoke_delegation(dp);
1836 else
1837 nfs4_put_stid(stid);
1838 break;
1839 case SC_TYPE_LAYOUT:
1840 nfsd4_close_layout(layoutstateid(stid));
1841 break;
1842 }
1843 }
1844
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-27 11:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 17:55 [PATCH v5 0/7] Automatic NFSv4 state revocation on filesystem unmount Chuck Lever
2026-03-26 17:55 ` [PATCH v5 1/7] NFSD: Extract revoke_one_stid() utility function Chuck Lever
2026-03-27 5:26 ` kernel test robot
2026-03-27 5:56 ` kernel test robot
2026-03-27 10:08 ` kernel test robot
2026-03-27 11:13 ` kernel test robot [this message]
2026-03-27 12:00 ` Jeff Layton
2026-03-27 12:21 ` Jeff Layton
2026-03-27 14:18 ` Chuck Lever
2026-03-26 17:55 ` [PATCH v5 2/7] NFSD: Add NFSD_CMD_UNLOCK_IP netlink command Chuck Lever
2026-03-27 12:06 ` Jeff Layton
2026-03-27 15:19 ` Chuck Lever
2026-03-27 15:52 ` Jeff Layton
2026-03-27 16:02 ` Chuck Lever
2026-03-26 17:55 ` [PATCH v5 3/7] NFSD: Add NFSD_CMD_UNLOCK_FILESYSTEM " Chuck Lever
2026-03-26 17:55 ` [PATCH v5 4/7] NFSD: Replace idr_for_each_entry_ul in find_one_sb_stid() Chuck Lever
2026-03-26 17:55 ` [PATCH v5 5/7] NFSD: Track svc_export in nfs4_stid Chuck Lever
2026-03-26 17:55 ` [PATCH v5 6/7] NFSD: Add NFSD_CMD_UNLOCK_EXPORT netlink command Chuck Lever
2026-03-26 17:55 ` [PATCH v5 7/7] NFSD: Close cached file handles when revoking export state Chuck Lever
2026-03-27 12:03 ` [PATCH v5 0/7] Automatic NFSv4 state revocation on filesystem unmount Jeff Layton
2026-03-27 13:29 ` Chuck Lever
2026-03-27 12:18 ` 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=202603271905.vZdE0ulk-lkp@intel.com \
--to=lkp@intel.com \
--cc=Dai.Ngo@oracle.com \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=neil@brown.name \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=okorniev@redhat.com \
--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.