From: kernel test robot <lkp@intel.com>
To: Raj Sahu <rjsu26@gmail.com>
Cc: llvm@lists.linux.dev, 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 21:12:25 +0800 [thread overview]
Message-ID: <202504202052.82sne6fn-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: x86_64-buildonly-randconfig-001-20250420 (https://download.01.org/0day-ci/archive/20250420/202504202052.82sne6fn-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250420/202504202052.82sne6fn-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/202504202052.82sne6fn-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/xen/smp.c:256:38: error: too few arguments to function call, single argument 'regs' was not specified
256 | generic_smp_call_function_interrupt();
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
include/linux/smp.h:176:6: note: 'generic_smp_call_function_single_interrupt' declared here
176 | void generic_smp_call_function_single_interrupt(struct pt_regs *regs);
| ^ ~~~~~~~~~~~~~~~~~~~~
arch/x86/xen/smp.c:264:45: error: too few arguments to function call, single argument 'regs' was not specified
264 | generic_smp_call_function_single_interrupt();
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
include/linux/smp.h:176:6: note: 'generic_smp_call_function_single_interrupt' declared here
176 | void generic_smp_call_function_single_interrupt(struct pt_regs *regs);
| ^ ~~~~~~~~~~~~~~~~~~~~
2 errors generated.
vim +/regs +256 arch/x86/xen/smp.c
f447d56d36af18 arch/x86/xen/smp.c Ben Guthro 2012-04-21 253
3b16cf87486143 arch/x86/xen/smp.c Jens Axboe 2008-06-26 254 static irqreturn_t xen_call_function_interrupt(int irq, void *dev_id)
3b16cf87486143 arch/x86/xen/smp.c Jens Axboe 2008-06-26 255 {
3b16cf87486143 arch/x86/xen/smp.c Jens Axboe 2008-06-26 @256 generic_smp_call_function_interrupt();
1b437c8c73a36d arch/x86/xen/smp.c Brian Gerst 2009-01-19 257 inc_irq_stat(irq_call_count);
f87e4cac4f4e94 arch/i386/xen/smp.c Jeremy Fitzhardinge 2007-07-17 258
3b16cf87486143 arch/x86/xen/smp.c Jens Axboe 2008-06-26 259 return IRQ_HANDLED;
3b16cf87486143 arch/x86/xen/smp.c Jens Axboe 2008-06-26 260 }
f87e4cac4f4e94 arch/i386/xen/smp.c Jeremy Fitzhardinge 2007-07-17 261
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2025-04-20 13:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250420105524.2115690-5-rjsu26@gmail.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=202504202052.82sne6fn-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox