All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Gabriele Monaco <gmonaco@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [glemco:staging_rv_bpf_monitors 20/29] kernel/trace/rv/rv_bpf.c:126:38: error: implicit declaration of function 'get_monitor_mdef_by_name'
Date: Fri, 06 Mar 2026 12:46:21 +0800	[thread overview]
Message-ID: <202603061228.fbMtrfDi-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/gmonaco/linux.git staging_rv_bpf_monitors
head:   3a153b8189ae2fb3a1e680f5092df636abbdac56
commit: 5c96c9aebafa7460b9d4335f84f4f643747750d8 [20/29] rv: Add reactors support to BPF monitors
config: parisc-allmodconfig (https://download.01.org/0day-ci/archive/20260306/202603061228.fbMtrfDi-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260306/202603061228.fbMtrfDi-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/202603061228.fbMtrfDi-lkp@intel.com/

All errors (new ones prefixed by >>):

   kernel/trace/rv/rv_bpf.c: In function 'bpf_rv_react':
>> kernel/trace/rv/rv_bpf.c:126:38: error: implicit declaration of function 'get_monitor_mdef_by_name' [-Wimplicit-function-declaration]
     126 |         struct rv_monitor *monitor = get_monitor_mdef_by_name(name__str);
         |                                      ^~~~~~~~~~~~~~~~~~~~~~~~
>> kernel/trace/rv/rv_bpf.c:126:38: error: initialization of 'struct rv_monitor *' from 'int' makes pointer from integer without a cast [-Wint-conversion]


vim +/get_monitor_mdef_by_name +126 kernel/trace/rv/rv_bpf.c

   115	
   116	/**
   117	 * bpf_rv_react - trigger a reactor from BPF
   118	 * @name: monitor name
   119	 * @msg: pre-formatted message string
   120	 *
   121	 * This kfunc allows BPF monitors to trigger reactors with a message.
   122	 * The message should be pre-formatted by the BPF program using bpf_snprintf.
   123	 */
   124	__bpf_kfunc void bpf_rv_react(char *name__str, char *msg)
   125	{
 > 126		struct rv_monitor *monitor = get_monitor_mdef_by_name(name__str);
   127	
   128		if (monitor)
   129			rv_react(monitor, "%s", msg);
   130	}
   131	

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

                 reply	other threads:[~2026-03-06  4:46 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=202603061228.fbMtrfDi-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=gmonaco@redhat.com \
    --cc=oe-kbuild-all@lists.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 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.