From: kernel test robot <lkp@intel.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: oe-kbuild-all@lists.linux.dev, Xiang Gao <xiang@kernel.org>,
linux-erofs@lists.ozlabs.org, Hongbo Li <lihongbo22@huawei.com>
Subject: [xiang-erofs:dev-test 9/10] fs/erofs/xattr.c:436:28: sparse: sparse: symbol 'erofs_xattr_user_handler' was not declared. Should it be static?
Date: Wed, 31 Dec 2025 17:02:48 +0800 [thread overview]
Message-ID: <202512311706.lMHnw10m-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git dev-test
head: e84fd1bdbe05e6b3ebe5766b98b7e4902203e8e1
commit: cb6528654a7fb2a3ffd55889fc877f61ca72edda [9/10] erofs: unexport erofs_xattr_prefix()
config: sh-randconfig-r134-20251231 (https://download.01.org/0day-ci/archive/20251231/202512311706.lMHnw10m-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251231/202512311706.lMHnw10m-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/202512311706.lMHnw10m-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/erofs/xattr.c:436:28: sparse: sparse: symbol 'erofs_xattr_user_handler' was not declared. Should it be static?
>> fs/erofs/xattr.c:443:28: sparse: sparse: symbol 'erofs_xattr_trusted_handler' was not declared. Should it be static?
vim +/erofs_xattr_user_handler +436 fs/erofs/xattr.c
89d80680577805 Gao Xiang 2025-12-29 435
89d80680577805 Gao Xiang 2025-12-29 @436 const struct xattr_handler erofs_xattr_user_handler = {
89d80680577805 Gao Xiang 2025-12-29 437 .prefix = XATTR_USER_PREFIX,
89d80680577805 Gao Xiang 2025-12-29 438 .flags = EROFS_XATTR_INDEX_USER,
89d80680577805 Gao Xiang 2025-12-29 439 .list = erofs_xattr_user_list,
89d80680577805 Gao Xiang 2025-12-29 440 .get = erofs_xattr_generic_get,
89d80680577805 Gao Xiang 2025-12-29 441 };
89d80680577805 Gao Xiang 2025-12-29 442
89d80680577805 Gao Xiang 2025-12-29 @443 const struct xattr_handler erofs_xattr_trusted_handler = {
89d80680577805 Gao Xiang 2025-12-29 444 .prefix = XATTR_TRUSTED_PREFIX,
89d80680577805 Gao Xiang 2025-12-29 445 .flags = EROFS_XATTR_INDEX_TRUSTED,
89d80680577805 Gao Xiang 2025-12-29 446 .list = erofs_xattr_trusted_list,
89d80680577805 Gao Xiang 2025-12-29 447 .get = erofs_xattr_generic_get,
89d80680577805 Gao Xiang 2025-12-29 448 };
89d80680577805 Gao Xiang 2025-12-29 449
:::::: The code at line 436 was first introduced by commit
:::::: 89d8068057780531fab06b928a80599b9762e461 erofs: unexport erofs_getxattr()
:::::: TO: Gao Xiang <hsiangkao@linux.alibaba.com>
:::::: CC: Gao Xiang <hsiangkao@linux.alibaba.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-31 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=202512311706.lMHnw10m-lkp@intel.com \
--to=lkp@intel.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=lihongbo22@huawei.com \
--cc=linux-erofs@lists.ozlabs.org \
--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