All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18 2/2] mm/page_size_compat.c:101:21: error: use of undeclared identifier 'bpf_map_fops'; did you mean 'bpf_map_put'?
Date: Fri, 10 Apr 2026 17:02:59 +0800	[thread overview]
Message-ID: <202604101625.iJPMFeIM-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android17-6.18
head:   08e21ebff803243bccd5e6cd4a8253ffebf74c64
commit: 156b58543560782fded68ccebbf252314d2d9ba7 [2/2] ANDROID: 16K: Adjust bpf ringbuffer pgoffset on 16K x86 emulation
config: arm-allnoconfig (https://download.01.org/0day-ci/archive/20260410/202604101625.iJPMFeIM-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project ae825cb8cea7f3ac8e5e4096f22713845cf5e501)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260410/202604101625.iJPMFeIM-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/202604101625.iJPMFeIM-lkp@intel.com/

All error/warnings (new ones prefixed by >>):

>> mm/page_size_compat.c:101:21: error: use of undeclared identifier 'bpf_map_fops'; did you mean 'bpf_map_put'?
     101 |         if (file->f_op != &bpf_map_fops)
         |                            ^~~~~~~~~~~~
         |                            bpf_map_put
   include/linux/bpf.h:3135:20: note: 'bpf_map_put' declared here
    3135 | static inline void bpf_map_put(struct bpf_map *map)
         |                    ^
>> mm/page_size_compat.c:101:17: warning: comparison of distinct pointer types ('const struct file_operations *' and 'void (*)(struct bpf_map *)') [-Wcompare-distinct-pointer-types]
     101 |         if (file->f_op != &bpf_map_fops)
         |             ~~~~~~~~~~ ^  ~~~~~~~~~~~~~
   1 warning and 1 error generated.


vim +101 mm/page_size_compat.c

    98	
    99	bool bpf_is_ringbuf_file(struct file *file)
   100	{
 > 101		if (file->f_op != &bpf_map_fops)
   102			return false;
   103	
   104		struct bpf_map *map = file->private_data;
   105	
   106		return map->map_type == BPF_MAP_TYPE_RINGBUF ||
   107			map->map_type == BPF_MAP_TYPE_USER_RINGBUF;
   108	}
   109	

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

                 reply	other threads:[~2026-04-10  9:03 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=202604101625.iJPMFeIM-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.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.