From: kernel test robot <lkp@intel.com>
To: Richard Sharpe <richard.sharpe@primarydata.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Anna Schumaker <Anna.Schumaker@Netapp.com>,
Lance Shelton <lance.shelton@hammerspace.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>
Subject: [linux-next:master 10745/12279] nfs4file.c:undefined reference to `__get_user_bad'
Date: Fri, 14 Jan 2022 20:57:34 +0800 [thread overview]
Message-ID: <202201142050.B1BDDw1x-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 468c1d50222ce9439c9835e00ab55ae9ced389fb
commit: bc66f68057662bbe9d3057f6896a646f3e0d1e9a [10745/12279] NFS: Support statx_get and statx_set ioctls
config: arm-mps2_defconfig (https://download.01.org/0day-ci/archive/20220114/202201142050.B1BDDw1x-lkp@intel.com/config)
compiler: arm-linux-gnueabi-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/next/linux-next.git/commit/?id=bc66f68057662bbe9d3057f6896a646f3e0d1e9a
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout bc66f68057662bbe9d3057f6896a646f3e0d1e9a
# 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=arm SHELL=/bin/bash
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 >>):
arm-linux-gnueabi-ld: fs/nfs/nfs4file.o: in function `nfs4_ioctl_file_statx_get':
>> nfs4file.c:(.text+0x3ac): undefined reference to `__get_user_bad'
arm-linux-gnueabi-ld: fs/nfs/nfs4file.o: in function `nfs_get_timespec64.constprop.0':
nfs4file.c:(.text+0x8ac): undefined reference to `__get_user_bad'
>> arm-linux-gnueabi-ld: nfs4file.c:(.text+0x8b4): undefined reference to `__get_user_bad'
arm-linux-gnueabi-ld: fs/nfs/nfs4file.o: in function `nfs4_ioctl_file_statx_set':
nfs4file.c:(.text+0x9a0): undefined reference to `__get_user_bad'
arm-linux-gnueabi-ld: nfs4file.c:(.text+0x9bc): undefined reference to `__get_user_bad'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-01-14 12:57 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=202201142050.B1BDDw1x-lkp@intel.com \
--to=lkp@intel.com \
--cc=Anna.Schumaker@Netapp.com \
--cc=kbuild-all@lists.01.org \
--cc=lance.shelton@hammerspace.com \
--cc=linux-mm@kvack.org \
--cc=richard.sharpe@primarydata.com \
--cc=trond.myklebust@hammerspace.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox