From: kbuild test robot <fengguang.wu@intel.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: kbuild-all@01.org, linux-nfs@vger.kernel.org
Subject: [nfs:ioctl 2/5] fs/nfs/ioctl.c:108: undefined reference to `__ucmpdi2'
Date: Sun, 17 Sep 2017 13:03:32 +0800 [thread overview]
Message-ID: <201709171326.NUSNFN7M%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2876 bytes --]
tree: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git ioctl
head: d60bb8b2798b19dd5a38f80012ba9c3a5f5a4436
commit: 33296e02268c7186bf01bf80e3d5aa8669b10488 [2/5] NFS: Add an ioctl to flush and invalidate a limited range of data
config: blackfin-BF561-ACVILON_defconfig (attached as .config)
compiler: bfin-uclinux-gcc (GCC) 6.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 33296e02268c7186bf01bf80e3d5aa8669b10488
# save the attached .config to linux build tree
make.cross ARCH=blackfin
All errors (new ones prefixed by >>):
bfin-uclinux-ld: L1 text overflow!
fs/nfs/ioctl.o: In function `nfs_ioctl_cachectl':
>> fs/nfs/ioctl.c:108: undefined reference to `__ucmpdi2'
vim +108 fs/nfs/ioctl.c
33296e02 Trond Myklebust 2012-11-14 99
1f0b13a9 Trond Myklebust 2012-11-14 100 static long nfs_ioctl_cachectl(struct file *filp, struct nfs_cachectl __user *argp)
1f0b13a9 Trond Myklebust 2012-11-14 101 {
1f0b13a9 Trond Myklebust 2012-11-14 102 u64 cmd;
1f0b13a9 Trond Myklebust 2012-11-14 103
1f0b13a9 Trond Myklebust 2012-11-14 104 if (!(filp->f_mode & (FMODE_READ|FMODE_WRITE)))
1f0b13a9 Trond Myklebust 2012-11-14 105 return -EBADF;
1f0b13a9 Trond Myklebust 2012-11-14 106 if (copy_from_user(&cmd, &argp->cmd, sizeof(cmd)))
1f0b13a9 Trond Myklebust 2012-11-14 107 return -EFAULT;
1f0b13a9 Trond Myklebust 2012-11-14 @108 switch (cmd) {
1f0b13a9 Trond Myklebust 2012-11-14 109 case NFS_CACHECTL_REVALIDATE_ALL:
1f0b13a9 Trond Myklebust 2012-11-14 110 return nfs_ioctl_cache_revalidate(filp, true, true);
1f0b13a9 Trond Myklebust 2012-11-14 111 case NFS_CACHECTL_REVALIDATE_METADATA:
1f0b13a9 Trond Myklebust 2012-11-14 112 return nfs_ioctl_cache_revalidate(filp, true, false);
1f0b13a9 Trond Myklebust 2012-11-14 113 case NFS_CACHECTL_REVALIDATE_DATA:
1f0b13a9 Trond Myklebust 2012-11-14 114 return nfs_ioctl_cache_revalidate(filp, false, true);
33296e02 Trond Myklebust 2012-11-14 115 case NFS_CACHECTL_REVALIDATE_RANGE:
33296e02 Trond Myklebust 2012-11-14 116 return nfs_ioctl_revalidate_range(filp, argp);
1f0b13a9 Trond Myklebust 2012-11-14 117 }
1f0b13a9 Trond Myklebust 2012-11-14 118 return -EINVAL;
1f0b13a9 Trond Myklebust 2012-11-14 119 }
1f0b13a9 Trond Myklebust 2012-11-14 120
:::::: The code at line 108 was first introduced by commit
:::::: 1f0b13a9d1c9c50891777988ada7e0bfaf8ead6d NFS: Add an ioctl to allow applications limited control over caching
:::::: TO: Trond Myklebust <Trond.Myklebust@netapp.com>
:::::: CC: Trond Myklebust <trond.myklebust@primarydata.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 15360 bytes --]
reply other threads:[~2017-09-17 5:04 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=201709171326.NUSNFN7M%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=Trond.Myklebust@netapp.com \
--cc=kbuild-all@01.org \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).