From: kbuild test robot <lkp@intel.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 171/199] waitq.c:(.text+0x80): multiple definition of `autofs_catatonic_mode'
Date: Fri, 18 May 2018 12:24:55 +0800 [thread overview]
Message-ID: <201805181253.jA3KBnp2%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4972 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 7400fc6942aefa2e009272d0e118284f110c5088
commit: 3d4478fa82f811fa49a51e037ba08c936758046e [171/199] kcov: prefault the kcov_area
config: sparc64-allyesconfig (attached as .config)
compiler: sparc64-linux-gnu-gcc (Debian 7.2.0-11) 7.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 3d4478fa82f811fa49a51e037ba08c936758046e
# save the attached .config to linux build tree
make.cross ARCH=sparc64
All errors (new ones prefixed by >>):
fs/autofs/inode.o: In function `autofs_new_ino':
inode.c:(.text+0x220): multiple definition of `autofs_new_ino'
fs/autofs/inode.o:inode.c:(.text+0x220): first defined here
fs/autofs/inode.o: In function `autofs_clean_ino':
inode.c:(.text+0x280): multiple definition of `autofs_clean_ino'
fs/autofs/inode.o:inode.c:(.text+0x280): first defined here
fs/autofs/inode.o: In function `autofs_free_ino':
inode.c:(.text+0x2c0): multiple definition of `autofs_free_ino'
fs/autofs/inode.o:inode.c:(.text+0x2c0): first defined here
fs/autofs/inode.o: In function `autofs_kill_sb':
inode.c:(.text+0x2e0): multiple definition of `autofs_kill_sb'
fs/autofs/inode.o:inode.c:(.text+0x2e0): first defined here
fs/autofs/inode.o: In function `autofs_get_inode':
inode.c:(.text+0x360): multiple definition of `autofs_get_inode'
fs/autofs/inode.o:inode.c:(.text+0x360): first defined here
fs/autofs/inode.o: In function `autofs_fill_super':
inode.c:(.text+0x440): multiple definition of `autofs_fill_super'
fs/autofs/inode.o:inode.c:(.text+0x440): first defined here
fs/autofs/root.o: In function `is_autofs_dentry':
root.c:(.text+0x1860): multiple definition of `is_autofs_dentry'
fs/autofs/root.o:root.c:(.text+0x1860): first defined here
fs/autofs/root.o:(.rodata+0x100): multiple definition of `autofs_dentry_operations'
fs/autofs/root.o:(.rodata+0x100): first defined here
fs/autofs/root.o:(.rodata+0x180): multiple definition of `autofs_dir_inode_operations'
fs/autofs/root.o:(.rodata+0x180): first defined here
fs/autofs/root.o:(.rodata+0x240): multiple definition of `autofs_dir_operations'
fs/autofs/root.o:(.rodata+0x240): first defined here
fs/autofs/root.o:(.rodata+0x338): multiple definition of `autofs_root_operations'
fs/autofs/root.o:(.rodata+0x338): first defined here
fs/autofs/symlink.o:(.rodata+0x0): multiple definition of `autofs_symlink_inode_operations'
fs/autofs/symlink.o:(.rodata+0x0): first defined here
fs/autofs/waitq.o: In function `autofs_catatonic_mode':
>> waitq.c:(.text+0x80): multiple definition of `autofs_catatonic_mode'
fs/autofs/waitq.o:waitq.c:(.text+0x80): first defined here
fs/autofs/waitq.o: In function `autofs_wait_release':
>> waitq.c:(.text+0x180): multiple definition of `autofs_wait_release'
fs/autofs/waitq.o:waitq.c:(.text+0x180): first defined here
fs/autofs/waitq.o: In function `autofs_wait':
>> waitq.c:(.text+0x520): multiple definition of `autofs_wait'
fs/autofs/waitq.o:waitq.c:(.text+0x520): first defined here
fs/autofs/expire.o: In function `autofs_expire_direct':
>> expire.c:(.text+0x7a0): multiple definition of `autofs_expire_direct'
fs/autofs/expire.o:expire.c:(.text+0x7a0): first defined here
fs/autofs/expire.o: In function `autofs_expire_indirect':
>> expire.c:(.text+0x8e0): multiple definition of `autofs_expire_indirect'
fs/autofs/expire.o:expire.c:(.text+0x8e0): first defined here
fs/autofs/expire.o: In function `autofs_expire_wait':
>> expire.c:(.text+0xba0): multiple definition of `autofs_expire_wait'
fs/autofs/expire.o:expire.c:(.text+0xba0): first defined here
fs/autofs/expire.o: In function `autofs_expire_run':
>> expire.c:(.text+0xce0): multiple definition of `autofs_expire_run'
fs/autofs/expire.o:expire.c:(.text+0xce0): first defined here
fs/autofs/expire.o: In function `autofs_do_expire_multi':
>> expire.c:(.text+0xde0): multiple definition of `autofs_do_expire_multi'
fs/autofs/expire.o:expire.c:(.text+0xde0): first defined here
fs/autofs/expire.o: In function `autofs_expire_multi':
>> expire.c:(.text+0xea0): multiple definition of `autofs_expire_multi'
fs/autofs/expire.o:expire.c:(.text+0xea0): first defined here
fs/autofs/dev-ioctl.o: In function `autofs_dev_ioctl_init':
>> dev-ioctl.c:(.init.text+0x0): multiple definition of `autofs_dev_ioctl_init'
fs/autofs/dev-ioctl.o:dev-ioctl.c:(.init.text+0x0): first defined here
fs/autofs/dev-ioctl.o: In function `autofs_dev_ioctl_exit':
>> dev-ioctl.c:(.text+0xbc0): multiple definition of `autofs_dev_ioctl_exit'
fs/autofs/dev-ioctl.o:dev-ioctl.c:(.text+0xbc0): first defined here
---
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: 53283 bytes --]
reply other threads:[~2018-05-18 4:25 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=201805181253.jA3KBnp2%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.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;
as well as URLs for NNTP newsgroup(s).