From: kernel test robot <lkp@intel.com>
To: Raj Sahu <rjsu26@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC bpf-next 4/4] bpf: Runtime part of fast-path termination approach
Date: Sun, 20 Apr 2025 20:50:53 +0800 [thread overview]
Message-ID: <202504202001.DtarnmV1-lkp@intel.com> (raw)
In-Reply-To: <20250420105524.2115690-5-rjsu26@gmail.com>
Hi Raj,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Raj-Sahu/bpf-Introduce-new-structs-and-struct-fields/20250420-185825
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link: https://lore.kernel.org/r/20250420105524.2115690-5-rjsu26%40gmail.com
patch subject: [RFC bpf-next 4/4] bpf: Runtime part of fast-path termination approach
config: arc-randconfig-001-20250420 (https://download.01.org/0day-ci/archive/20250420/202504202001.DtarnmV1-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250420/202504202001.DtarnmV1-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/202504202001.DtarnmV1-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/lockdep.h:14,
from include/linux/spinlock.h:63,
from arch/arc/kernel/smp.c:12:
arch/arc/kernel/smp.c: In function '__do_IPI':
>> include/linux/smp.h:178:9: error: too few arguments to function 'generic_smp_call_function_single_interrupt'
178 | generic_smp_call_function_single_interrupt
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/smp.h:178:9: note: in definition of macro 'generic_smp_call_function_interrupt'
178 | generic_smp_call_function_single_interrupt
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/smp.h:176:6: note: declared here
176 | void generic_smp_call_function_single_interrupt(struct pt_regs *regs);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/generic_smp_call_function_single_interrupt +178 include/linux/smp.h
f37f435f33717d Thomas Gleixner 2012-05-07 171
3d4422332711ef Jens Axboe 2008-06-26 172 /*
3d4422332711ef Jens Axboe 2008-06-26 173 * Generic and arch helpers
3d4422332711ef Jens Axboe 2008-06-26 174 */
d8ad7d1123a960 Takao Indoh 2011-03-29 175 void __init call_function_init(void);
74a62e27c20ef9 sidchintamaneni 2025-04-20 176 void generic_smp_call_function_single_interrupt(struct pt_regs *regs);
9a46ad6d6df3b5 Shaohua Li 2013-02-21 177 #define generic_smp_call_function_interrupt \
9a46ad6d6df3b5 Shaohua Li 2013-02-21 @178 generic_smp_call_function_single_interrupt
a3bc0dbc81d36f Andrew Morton 2006-09-25 179
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-04-20 12:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-20 10:55 [RFC bpf-next 0/4] bpf: Fast-Path approach for BPF program Termination Raj Sahu
2025-04-20 10:55 ` [RFC bpf-next 1/4] bpf: Introduce new structs and struct fields Raj Sahu
2025-05-13 0:04 ` Eduard Zingerman
2025-04-20 10:55 ` [RFC bpf-next 2/4] bpftool/libbpf : Introduce bpf_prog_termination to trigger termination signal Raj Sahu
2025-04-20 10:55 ` [RFC bpf-next 3/4] bpf: Generating a stubbed version of BPF program for termination Raj Sahu
2025-04-20 13:01 ` kernel test robot
2025-04-20 13:01 ` kernel test robot
2025-04-20 13:01 ` kernel test robot
2025-05-13 0:07 ` Eduard Zingerman
2025-05-13 0:20 ` Alexei Starovoitov
2025-05-13 4:40 ` Eduard Zingerman
2025-05-13 5:16 ` Siddharth Chintamaneni
2025-05-15 1:59 ` Alexei Starovoitov
2025-05-15 17:43 ` Andrii Nakryiko
2025-05-17 5:01 ` Raj Sahu
2025-05-19 1:20 ` Alexei Starovoitov
2025-05-28 7:10 ` Raj Sahu
2025-06-04 23:02 ` Alexei Starovoitov
2025-06-10 22:06 ` Siddharth Chintamaneni
2025-06-11 15:59 ` Alexei Starovoitov
2025-04-20 10:55 ` [RFC bpf-next 4/4] bpf: Runtime part of fast-path termination approach Raj Sahu
2025-04-20 12:50 ` kernel test robot [this message]
2025-04-20 13:12 ` kernel test robot
2025-04-20 14:15 ` kernel test robot
2025-05-05 20:13 ` [RFC bpf-next 0/4] bpf: Fast-Path approach for BPF program Termination Kumar Kartikeya Dwivedi
2025-05-06 5:55 ` Raj Sahu
2025-05-06 22:45 ` Alexei Starovoitov
2025-05-06 22:59 ` Kumar Kartikeya Dwivedi
2025-05-07 0:32 ` Alexei Starovoitov
2025-05-07 0:38 ` Kumar Kartikeya Dwivedi
2025-05-07 1:15 ` Alexei Starovoitov
2025-05-07 2:10 ` Kumar Kartikeya Dwivedi
2025-05-07 3:36 ` Alexei Starovoitov
2025-05-07 5:04 ` Kumar Kartikeya Dwivedi
2025-05-07 18:15 ` Zvi Effron
2025-05-07 20:01 ` Alexei Starovoitov
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=202504202001.DtarnmV1-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rjsu26@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.