From: kernel test robot <lkp@intel.com>
To: Ye Bin <yebin10@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
"Theodore Ts'o" <tytso@mit.edu>, Jan Kara <jack@suse.cz>
Subject: fs/ext4/extents-test.c:59:3: sparse: sparse: symbol 'k_ctx' was not declared. Should it be static?
Date: Tue, 22 Sep 2026 19:42:05 +0800 [thread overview]
Message-ID: <202609221900.Pgwrcp41-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: f0100363d8c374bd8e9ea7c9ba02744f0b802ca4
commit: 9e1b14320b154094bb2c1bee6d8c6cb851fc3215 ext4: fix extents-test.c is not compiled when EXT4_KUNIT_TESTS=M
date: 6 months ago
config: x86_64-randconfig-1300-20260922 (https://download.01.org/0day-ci/archive/20260922/202609221900.Pgwrcp41-lkp@intel.com/config)
compiler: gcc-13 (Debian 13.3.0-16) 13.3.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260922/202609221900.Pgwrcp41-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
| Fixes: 9e1b14320b15 ("ext4: fix extents-test.c is not compiled when EXT4_KUNIT_TESTS=M")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609221900.Pgwrcp41-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/ext4/extents-test.c:59:3: sparse: sparse: symbol 'k_ctx' was not declared. Should it be static?
vim +/k_ctx +59 fs/ext4/extents-test.c
cb1e0c1d1fad5b Ojaswin Mujoo 2026-01-23 49
cb1e0c1d1fad5b Ojaswin Mujoo 2026-01-23 50 struct kunit_ctx {
cb1e0c1d1fad5b Ojaswin Mujoo 2026-01-23 51 /*
cb1e0c1d1fad5b Ojaswin Mujoo 2026-01-23 52 * Ext4 inode which has only 1 unwrit extent
cb1e0c1d1fad5b Ojaswin Mujoo 2026-01-23 53 */
cb1e0c1d1fad5b Ojaswin Mujoo 2026-01-23 54 struct ext4_inode_info *k_ei;
cb1e0c1d1fad5b Ojaswin Mujoo 2026-01-23 55 /*
cb1e0c1d1fad5b Ojaswin Mujoo 2026-01-23 56 * Represents the underlying data area (used for zeroout testing)
cb1e0c1d1fad5b Ojaswin Mujoo 2026-01-23 57 */
cb1e0c1d1fad5b Ojaswin Mujoo 2026-01-23 58 char *k_data;
cb1e0c1d1fad5b Ojaswin Mujoo 2026-01-23 @59 } k_ctx;
cb1e0c1d1fad5b Ojaswin Mujoo 2026-01-23 60
:::::: The code at line 59 was first introduced by commit
:::::: cb1e0c1d1fad5bfad90d80c74ebdb53796d8a2db ext4: kunit tests for extent splitting and conversion
:::::: TO: Ojaswin Mujoo <ojaswin@linux.ibm.com>
:::::: CC: Theodore Ts'o <tytso@mit.edu>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-09-22 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 11:42 kernel test robot [this message]
2026-09-22 13:59 ` Ojaswin Mujoo
-- strict thread matches above, loose matches on Subject: below --
2026-03-02 9:23 kernel test robot
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=202609221900.Pgwrcp41-lkp@intel.com \
--to=lkp@intel.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tytso@mit.edu \
--cc=yebin10@huawei.com \
/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®