All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Hannes Reinecke <hare@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [hare-nvme:configfs-ns 1/9] drivers/nvme/target/bpf_ops.c:25:16: error: implicit declaration of function 'bpf_tracing_btf_ctx_access'
Date: Sat, 09 May 2026 02:08:23 +0800	[thread overview]
Message-ID: <202605090205.CEh9SC9R-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/hare/nvme.git configfs-ns
head:   509cbb083b05db0f02a3ceea68bb093f8725a6a5
commit: 94040dcdf8d7b146f62dfb3e0156d93a9713880d [1/9] nvmet-bpf: eBPF struct_ops support for log pages
config: loongarch-randconfig-001-20260509 (https://download.01.org/0day-ci/archive/20260509/202605090205.CEh9SC9R-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260509/202605090205.CEh9SC9R-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/202605090205.CEh9SC9R-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/nvme/target/bpf_ops.c: In function 'nvmet_bpf_ops_is_valid_access':
>> drivers/nvme/target/bpf_ops.c:25:16: error: implicit declaration of function 'bpf_tracing_btf_ctx_access' [-Wimplicit-function-declaration]
      25 |         return bpf_tracing_btf_ctx_access(off, size, type, prog, info);
         |                ^~~~~~~~~~~~~~~~~~~~~~~~~~
   In file included from include/linux/bpf_verifier.h:7,
                    from drivers/nvme/target/bpf_ops.c:4:
   drivers/nvme/target/bpf_ops.c: In function 'nvmet_bpf_struct_ops_init':
   include/linux/bpf.h:2142:50: warning: statement with no effect [-Wunused-value]
    2142 | #define register_bpf_struct_ops(st_ops, type) ({ (void *)(st_ops); 0; })
         |                                                  ^~~~~~~~~~~~~~~~
   drivers/nvme/target/bpf_ops.c:309:15: note: in expansion of macro 'register_bpf_struct_ops'
     309 |         ret = register_bpf_struct_ops(&bpf_nvmet_bpf_ops, nvmet_bpf_ops);
         |               ^~~~~~~~~~~~~~~~~~~~~~~


vim +/bpf_tracing_btf_ctx_access +25 drivers/nvme/target/bpf_ops.c

    19	
    20	static bool nvmet_bpf_ops_is_valid_access(int off, int size,
    21						  enum bpf_access_type type,
    22						  const struct bpf_prog *prog,
    23						  struct bpf_insn_access_aux *info)
    24	{
  > 25		return bpf_tracing_btf_ctx_access(off, size, type, prog, info);
    26	}
    27	

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

                 reply	other threads:[~2026-05-08 18:09 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=202605090205.CEh9SC9R-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hare@kernel.org \
    --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.