The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [cel:topic-nfsd-tracepoints 51/162] mipsel-linux-ld: fs/lockd/xdrtrace.o:(__tracepoints+0x0): multiple definition of `__tracepoint_decode_voidargs'; fs/nfsd/xdrtrace.o:(__tracepoints+0x840): first defined here
Date: Thu, 18 Nov 2021 20:58:07 +0800	[thread overview]
Message-ID: <202111182001.lNMx4o67-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1871 bytes --]

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux topic-nfsd-tracepoints
head:   4f44bfc71b2fdbce5b8b0a85e1b6937ccb6c3977
commit: 9c7eb0f8cb451e64aac52bf42c91b952633b943d [51/162] lockd: Add a tracepoint to record decoded NLM void arguments
config: mips-malta_kvm_defconfig (attached as .config)
compiler: mipsel-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/cel/linux.git/commit/?id=9c7eb0f8cb451e64aac52bf42c91b952633b943d
        git remote add cel git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux
        git fetch --no-tags cel topic-nfsd-tracepoints
        git checkout 9c7eb0f8cb451e64aac52bf42c91b952633b943d
        # 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=mips 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 >>):

   mipsel-linux-ld: fs/lockd/xdrtrace.o: in function `__traceiter_decode_voidargs':
>> xdrtrace.c:(.text+0x0): multiple definition of `__traceiter_decode_voidargs'; fs/nfsd/xdrtrace.o:xdrtrace.c:(.text+0x0): first defined here
>> mipsel-linux-ld: fs/lockd/xdrtrace.o:(__tracepoints+0x0): multiple definition of `__tracepoint_decode_voidargs'; fs/nfsd/xdrtrace.o:(__tracepoints+0x840): first defined here
>> mipsel-linux-ld: fs/lockd/xdrtrace.o:(.data+0x120): multiple definition of `__SCK__tp_func_decode_voidargs'; fs/nfsd/xdrtrace.o:(.data+0x56a0): first defined here

---
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: 21367 bytes --]

                 reply	other threads:[~2021-11-18 13:00 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=202111182001.lNMx4o67-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=chuck.lever@oracle.com \
    --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