public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>,
	bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com,
	eddyz87@gmail.com, memxor@gmail.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Mykyta Yatsenko <yatsenko@meta.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH bpf-next v6 3/6] bpf: Add sleepable support for classic tracepoint programs
Date: Fri, 27 Mar 2026 20:18:02 +0800	[thread overview]
Message-ID: <202603272034.xdMLP5lS-lkp@intel.com> (raw)
In-Reply-To: <20260325-sleepable_tracepoints-v6-3-2b182dacea13@meta.com>

Hi Mykyta,

kernel test robot noticed the following build errors:

[auto build test ERROR on 6c8e1a9eee0fec802b542dadf768c30c2a183b3c]

url:    https://github.com/intel-lab-lkp/linux/commits/Mykyta-Yatsenko/bpf-Add-sleepable-support-for-raw-tracepoint-programs/20260327-132324
base:   6c8e1a9eee0fec802b542dadf768c30c2a183b3c
patch link:    https://lore.kernel.org/r/20260325-sleepable_tracepoints-v6-3-2b182dacea13%40meta.com
patch subject: [PATCH bpf-next v6 3/6] bpf: Add sleepable support for classic tracepoint programs
config: sparc64-defconfig (https://download.01.org/0day-ci/archive/20260327/202603272034.xdMLP5lS-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260327/202603272034.xdMLP5lS-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202603272034.xdMLP5lS-lkp@intel.com/

All errors (new ones prefixed by >>):

>> ld.lld: error: duplicate symbol: bpf_prog_inc_misses_counter
   >>> defined at mdio_bus.c
   >>>            drivers/net/phy/mdio_bus.o:(bpf_prog_inc_misses_counter)
   >>> defined at mdio_device.c
   >>>            drivers/net/phy/mdio_device.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: bpf_prog_inc_misses_counter
   >>> defined at phy.c
   >>>            drivers/net/phy/phy.o:(bpf_prog_inc_misses_counter)
   >>> defined at phy-c45.c
   >>>            drivers/net/phy/phy-c45.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: bpf_prog_inc_misses_counter
   >>> defined at phy.c
   >>>            drivers/net/phy/phy.o:(bpf_prog_inc_misses_counter)
   >>> defined at phy-core.c
   >>>            drivers/net/phy/phy-core.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: bpf_prog_inc_misses_counter
   >>> defined at phy.c
   >>>            drivers/net/phy/phy.o:(bpf_prog_inc_misses_counter)
   >>> defined at linkmode.c
   >>>            drivers/net/phy/linkmode.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: bpf_prog_inc_misses_counter
   >>> defined at phy.c
   >>>            drivers/net/phy/phy.o:(bpf_prog_inc_misses_counter)
   >>> defined at phy_device.c
   >>>            drivers/net/phy/phy_device.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: bpf_prog_inc_misses_counter
   >>> defined at phy.c
   >>>            drivers/net/phy/phy.o:(bpf_prog_inc_misses_counter)
   >>> defined at phy_link_topology.c
   >>>            drivers/net/phy/phy_link_topology.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: bpf_prog_inc_misses_counter
   >>> defined at phy.c
   >>>            drivers/net/phy/phy.o:(bpf_prog_inc_misses_counter)
   >>> defined at phy_caps.c
   >>>            drivers/net/phy/phy_caps.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: bpf_prog_inc_misses_counter
   >>> defined at phy.c
   >>>            drivers/net/phy/phy.o:(bpf_prog_inc_misses_counter)
   >>> defined at phy_port.c
   >>>            drivers/net/phy/phy_port.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: bpf_prog_inc_misses_counter
   >>> defined at phy.c
   >>>            drivers/net/phy/phy.o:(bpf_prog_inc_misses_counter)
   >>> defined at mdio_bus_provider.c
   >>>            drivers/net/phy/mdio_bus_provider.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: bpf_prog_inc_misses_counter
   >>> defined at phy.c
   >>>            drivers/net/phy/phy.o:(bpf_prog_inc_misses_counter)
   >>> defined at swphy.c
   >>>            drivers/net/phy/swphy.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: bpf_prog_inc_misses_counter
   >>> defined at vlan.c
   >>>            net/8021q/vlan.o:(bpf_prog_inc_misses_counter)
   >>> defined at vlan_netlink.c
   >>>            net/8021q/vlan_netlink.o:(.text+0x0)
..

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

           reply	other threads:[~2026-03-27 12:18 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20260325-sleepable_tracepoints-v6-3-2b182dacea13@meta.com>]

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=202603272034.xdMLP5lS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=kafai@meta.com \
    --cc=kernel-team@meta.com \
    --cc=llvm@lists.linux.dev \
    --cc=memxor@gmail.com \
    --cc=mykyta.yatsenko5@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=yatsenko@meta.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