From: kernel test robot <lkp@intel.com>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [kkdwivedi:fermata 40/49] kernel/bpf/blk.c:127:17: sparse: sparse: symbol 'bpf_blk_close' was not declared. Should it be static?
Date: Fri, 02 Oct 2026 15:47:26 +0200 [thread overview]
Message-ID: <202610021546.Gfji4DAs-lkp@intel.com> (raw)
tree: https://github.com/kkdwivedi/linux fermata
head: babde5051be3840becf5a78de91a0b68a99f0e49
commit: be75423b67d512b1abdea0cc7cbef17ffd7e8040 [40/49] bpf: Add block device reads that complete into a coroutine
config: um-randconfig-r2307-20261001 (https://download.01.org/0day-ci/archive/20261002/202610021546.Gfji4DAs-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.4.0-5) 12.4.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261002/202610021546.Gfji4DAs-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/202610021546.Gfji4DAs-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/bpf/blk.c:127:17: sparse: sparse: symbol 'bpf_blk_close' was not declared. Should it be static?
vim +/bpf_blk_close +127 kernel/bpf/blk.c
119
120 /**
121 * bpf_blk_close - close a device opened with bpf_blk_open()
122 * @major: device major number
123 * @minor: device minor number
124 *
125 * Reads in flight complete; reads submitted after this fail with -ENODEV.
126 */
> 127 __bpf_kfunc int bpf_blk_close(u32 major, u32 minor)
128 {
129 struct bpf_blk_dev *d;
130
131 mutex_lock(&bpf_blk_mutex);
132 d = xa_erase(&bpf_blk_devs, MKDEV(major, minor));
133 mutex_unlock(&bpf_blk_mutex);
134 if (!d)
135 return -ENODEV;
136 call_rcu(&d->rcu, bpf_blk_dev_free);
137 pr_info("bpf_blk: close %u:%u: %lld reads submitted, %lld completed, %lld frames resumed\n",
138 major, minor, (long long)atomic64_read(&bpf_blk_submitted),
139 (long long)atomic64_read(&bpf_blk_completed),
140 (long long)atomic64_read(&bpf_blk_resumed));
141 return 0;
142 }
143
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-02 13:48 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=202610021546.Gfji4DAs-lkp@intel.com \
--to=lkp@intel.com \
--cc=memxor@gmail.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.