From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-6.1 2/2] drivers/dma-buf/heaps/page_pool.c:235:17: sparse: sparse: symbol 'pool_shrinker' was not declared. Should it be static?
Date: Tue, 27 Oct 2026 07:51:45 +0100 [thread overview]
Message-ID: <202610270749.TnClUGgT-lkp@intel.com> (raw)
Hi Hridya,
First bad commit (maybe != root cause):
tree: https://android.googlesource.com/kernel/common android14-6.1
head: e7e4a657fff86db1dc8f902e5ff8c713b81f6d39
commit: 70ad75e771d15cdf21f43548ee47bb38b4c2f564 [2/2] ANDROID: dma-heap: Make the page-pool library built-in
config: arm-randconfig-r2308-20261027 (https://download.01.org/0day-ci/archive/20261027/202610270749.TnClUGgT-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 42d4451d86c175b745d6ea1c4081787994c7259b)
sparse: v0.6.5-rc1-1-gc4640450
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261027/202610270749.TnClUGgT-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/202610270749.TnClUGgT-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/dma-buf/heaps/page_pool.c:235:17: sparse: sparse: symbol 'pool_shrinker' was not declared. Should it be static?
drivers/dma-buf/heaps/page_pool.c:242:5: sparse: sparse: symbol 'dmabuf_page_pool_init_shrinker' was not declared. Should it be static?
vim +/pool_shrinker +235 drivers/dma-buf/heaps/page_pool.c
d3b59a75e86384 John Stultz 2020-10-02 234
d3b59a75e86384 John Stultz 2020-10-02 @235 struct shrinker pool_shrinker = {
d3b59a75e86384 John Stultz 2020-10-02 236 .count_objects = dmabuf_page_pool_shrink_count,
d3b59a75e86384 John Stultz 2020-10-02 237 .scan_objects = dmabuf_page_pool_shrink_scan,
d3b59a75e86384 John Stultz 2020-10-02 238 .seeks = DEFAULT_SEEKS,
d3b59a75e86384 John Stultz 2020-10-02 239 .batch = 0,
d3b59a75e86384 John Stultz 2020-10-02 240 };
d3b59a75e86384 John Stultz 2020-10-02 241
:::::: The code at line 235 was first introduced by commit
:::::: d3b59a75e86384b6d5302159fa89446ead81e71e ANDROID: dma-buf: heaps: Add a shrinker controlled page pool
:::::: TO: John Stultz <john.stultz@linaro.org>
:::::: CC: Greg Kroah-Hartman <gregkh@google.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-27 6:52 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=202610270749.TnClUGgT-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.