From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jlayton:locks-5.15 4/4] fs/nfsd/vfs.c:349:17: error: label 'out_nfserrno' used but not defined
Date: Sat, 21 Aug 2021 06:05:23 +0800 [thread overview]
Message-ID: <202108210614.VrwhFmVR-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3484 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git locks-5.15
head: 85ac8b1a5a1af87f5e66bf45ae3aeee4da931044
commit: 85ac8b1a5a1af87f5e66bf45ae3aeee4da931044 [4/4] fs: remove mandatory file locking support
config: parisc-defconfig (attached as .config)
compiler: hppa-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://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git/commit/?id=85ac8b1a5a1af87f5e66bf45ae3aeee4da931044
git remote add jlayton https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git
git fetch --no-tags jlayton locks-5.15
git checkout 85ac8b1a5a1af87f5e66bf45ae3aeee4da931044
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=parisc 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 errors (new ones prefixed by >>):
fs/nfsd/vfs.c: In function 'nfsd_get_write_access':
>> fs/nfsd/vfs.c:349:17: error: label 'out_nfserrno' used but not defined
349 | goto out_nfserrno;
| ^~~~
vim +/out_nfserrno +349 fs/nfsd/vfs.c
818e5a22e907fba Christoph Hellwig 2013-11-18 330
0839ffb83e44e5f J. Bruce Fields 2017-02-09 331 static __be32
0839ffb83e44e5f J. Bruce Fields 2017-02-09 332 nfsd_get_write_access(struct svc_rqst *rqstp, struct svc_fh *fhp,
0839ffb83e44e5f J. Bruce Fields 2017-02-09 333 struct iattr *iap)
0839ffb83e44e5f J. Bruce Fields 2017-02-09 334 {
0839ffb83e44e5f J. Bruce Fields 2017-02-09 335 struct inode *inode = d_inode(fhp->fh_dentry);
0839ffb83e44e5f J. Bruce Fields 2017-02-09 336 int host_err;
0839ffb83e44e5f J. Bruce Fields 2017-02-09 337
0839ffb83e44e5f J. Bruce Fields 2017-02-09 338 if (iap->ia_size < inode->i_size) {
0839ffb83e44e5f J. Bruce Fields 2017-02-09 339 __be32 err;
0839ffb83e44e5f J. Bruce Fields 2017-02-09 340
0839ffb83e44e5f J. Bruce Fields 2017-02-09 341 err = nfsd_permission(rqstp, fhp->fh_export, fhp->fh_dentry,
0839ffb83e44e5f J. Bruce Fields 2017-02-09 342 NFSD_MAY_TRUNC | NFSD_MAY_OWNER_OVERRIDE);
0839ffb83e44e5f J. Bruce Fields 2017-02-09 343 if (err)
0839ffb83e44e5f J. Bruce Fields 2017-02-09 344 return err;
0839ffb83e44e5f J. Bruce Fields 2017-02-09 345 }
0839ffb83e44e5f J. Bruce Fields 2017-02-09 346
0839ffb83e44e5f J. Bruce Fields 2017-02-09 347 host_err = get_write_access(inode);
0839ffb83e44e5f J. Bruce Fields 2017-02-09 348 if (host_err)
0839ffb83e44e5f J. Bruce Fields 2017-02-09 @349 goto out_nfserrno;
0839ffb83e44e5f J. Bruce Fields 2017-02-09 350
0839ffb83e44e5f J. Bruce Fields 2017-02-09 351 return nfserrno(host_err);
0839ffb83e44e5f J. Bruce Fields 2017-02-09 352 }
0839ffb83e44e5f J. Bruce Fields 2017-02-09 353
:::::: The code at line 349 was first introduced by commit
:::::: 0839ffb83e44e5ff1843e932592525fc2bff23ff nfsd: Revert "nfsd: special case truncates some more"
:::::: TO: J. Bruce Fields <bfields@redhat.com>
:::::: CC: J. Bruce Fields <bfields@redhat.com>
---
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: 18672 bytes --]
reply other threads:[~2021-08-20 22:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202108210614.VrwhFmVR-lkp@intel.com \
--to=lkp@intel.com \
--cc=jlayton@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@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