From: kernel test robot <lkp@intel.com>
To: Deepanshu Kartikey <kartikey406@gmail.com>,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
olsajiri@gmail.com, irogers@google.com, adrian.hunter@intel.com,
james.clark@linaro.org, kpsingh@kernel.org, matt@bobrowski.net,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, emil@etsalapatis.com,
ihor.solodrai@linux.dev, rostedt@goodmis.org,
mhiramat@kernel.org, mathieu.desnoyers@efficios.com
Cc: oe-kbuild-all@lists.linux.dev, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] perf/bpf: Fix lockless access to parent_event->prog in perf_event_alloc()
Date: Tue, 25 Aug 2026 07:58:02 +0800 [thread overview]
Message-ID: <202608250735.Idi1PQgE-lkp@intel.com> (raw)
In-Reply-To: <20260821014210.18681-1-kartikey406@gmail.com>
Hi Deepanshu,
kernel test robot noticed the following build errors:
[auto build test ERROR on perf-tools-next/perf-tools-next]
[also build test ERROR on tip/perf/core perf-tools/perf-tools linus/master v7.2 next-20260821]
[cannot apply to acme/perf/core]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Deepanshu-Kartikey/perf-bpf-Fix-lockless-access-to-parent_event-prog-in-perf_event_alloc/20260821-071210
base: https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git perf-tools-next
patch link: https://lore.kernel.org/r/20260821014210.18681-1-kartikey406%40gmail.com
patch subject: [PATCH] perf/bpf: Fix lockless access to parent_event->prog in perf_event_alloc()
config: arm-randconfig-004-20260825 (https://download.01.org/0day-ci/archive/20260825/202608250735.Idi1PQgE-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260825/202608250735.Idi1PQgE-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/202608250735.Idi1PQgE-lkp@intel.com/
All errors (new ones prefixed by >>):
arm-linux-gnueabi-ld: kernel/events/core.o: in function `__list_add':
>> include/linux/list.h:159:(.text.perf_event_alloc.part.0+0x96c): undefined reference to `bpf_event_mutex'
arm-linux-gnueabi-ld: drivers/pci/controller/cadence/pcie-cadence-plat.o: in function `cdns_plat_pcie_probe':
drivers/pci/controller/cadence/pcie-cadence-plat.c:85:(.text.cdns_plat_pcie_probe+0xfc): undefined reference to `cdns_pcie_host_setup'
vim +159 include/linux/list.h
d7c816733d501b5 Kees Cook 2016-08-17 147
^1da177e4c3f415 Linus Torvalds 2005-04-16 148 /*
^1da177e4c3f415 Linus Torvalds 2005-04-16 149 * Insert a new entry between two known consecutive entries.
^1da177e4c3f415 Linus Torvalds 2005-04-16 150 *
^1da177e4c3f415 Linus Torvalds 2005-04-16 151 * This is only for internal list manipulation where we know
^1da177e4c3f415 Linus Torvalds 2005-04-16 152 * the prev/next entries already!
^1da177e4c3f415 Linus Torvalds 2005-04-16 153 */
^1da177e4c3f415 Linus Torvalds 2005-04-16 154 static inline void __list_add(struct list_head *new,
^1da177e4c3f415 Linus Torvalds 2005-04-16 155 struct list_head *prev,
^1da177e4c3f415 Linus Torvalds 2005-04-16 156 struct list_head *next)
^1da177e4c3f415 Linus Torvalds 2005-04-16 157 {
d7c816733d501b5 Kees Cook 2016-08-17 158 if (!__list_add_valid(new, prev, next))
d7c816733d501b5 Kees Cook 2016-08-17 @159 return;
d7c816733d501b5 Kees Cook 2016-08-17 160
^1da177e4c3f415 Linus Torvalds 2005-04-16 161 next->prev = new;
^1da177e4c3f415 Linus Torvalds 2005-04-16 162 new->next = next;
^1da177e4c3f415 Linus Torvalds 2005-04-16 163 new->prev = prev;
1c97be677f72b3c Paul E. McKenney 2015-09-20 164 WRITE_ONCE(prev->next, new);
^1da177e4c3f415 Linus Torvalds 2005-04-16 165 }
^1da177e4c3f415 Linus Torvalds 2005-04-16 166
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-08-24 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 1:42 [PATCH] perf/bpf: Fix lockless access to parent_event->prog in perf_event_alloc() Deepanshu Kartikey
2026-08-21 1:56 ` sashiko-bot
2026-08-21 2:32 ` bot+bpf-ci
2026-08-21 18:33 ` Andrii Nakryiko
2026-08-25 1:38 ` Deepanshu Kartikey
2026-08-24 22:52 ` kernel test robot
2026-08-24 23:58 ` kernel test robot [this message]
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=202608250735.Idi1PQgE-lkp@intel.com \
--to=lkp@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kartikey406@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=matt@bobrowski.net \
--cc=memxor@gmail.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=olsajiri@gmail.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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