From: kernel test robot <lkp@intel.com>
To: Bo Liu <liubo03@inspur.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Gao Xiang <xiang@kernel.org>
Subject: fs/erofs/decompressor_crypto.c:64:30: sparse: sparse: symbol 'z_erofs_crypto' was not declared. Should it be static?
Date: Wed, 10 Dec 2025 21:09:16 +0800 [thread overview]
Message-ID: <202512102025.4mWeBSsf-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: c9b47175e9131118e6f221cc8fb81397d62e7c91
commit: b4a29efc51461edf1a02e9da656d4480cabd24b0 erofs: support DEFLATE decompression by using Intel QAT
date: 7 months ago
config: s390-randconfig-r111-20251210 (https://download.01.org/0day-ci/archive/20251210/202512102025.4mWeBSsf-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251210/202512102025.4mWeBSsf-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/202512102025.4mWeBSsf-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/erofs/decompressor_crypto.c:64:30: sparse: sparse: symbol 'z_erofs_crypto' was not declared. Should it be static?
vim +/z_erofs_crypto +64 fs/erofs/decompressor_crypto.c
63
> 64 struct z_erofs_crypto_engine *z_erofs_crypto[Z_EROFS_COMPRESSION_MAX] = {
65 [Z_EROFS_COMPRESSION_LZ4] = (struct z_erofs_crypto_engine[]) {
66 {},
67 },
68 [Z_EROFS_COMPRESSION_LZMA] = (struct z_erofs_crypto_engine[]) {
69 {},
70 },
71 [Z_EROFS_COMPRESSION_DEFLATE] = (struct z_erofs_crypto_engine[]) {
72 { .crypto_name = "qat_deflate", },
73 {},
74 },
75 [Z_EROFS_COMPRESSION_ZSTD] = (struct z_erofs_crypto_engine[]) {
76 {},
77 },
78 };
79 static DECLARE_RWSEM(z_erofs_crypto_rwsem);
80
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-10 13:10 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=202512102025.4mWeBSsf-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liubo03@inspur.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=xiang@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®