fs/ext4/extents-test.c:59:3: sparse: sparse: symbol 'k_ctx' was not declared. Should it be static?

fs/ext4/extents-test.c:59:3: sparse: sparse: symbol 'k_ctx' was not declared. Should it be static?

[kernel test robot]

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

Re: fs/ext4/extents-test.c:59:3: sparse: sparse: symbol 'k_ctx' was not declared. Should it be static?

[Ojaswin Mujoo]

On Tue, Sep 22, 2026 at 07:42:05PM +0800, kernel test robot wrote:
> 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?

Yes, seems like a legit warning when EXT4_KUNIT_TESTS=m. I'll send a
fix.

Thanks,
ojaswin

> 
> 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

fs/ext4/extents-test.c:59:3: sparse: sparse: symbol 'k_ctx' was not declared. Should it be static?

[kernel test robot]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   11439c4635edd669ae435eec308f4ab8a0804808
commit: cb1e0c1d1fad5bfad90d80c74ebdb53796d8a2db ext4: kunit tests for extent splitting and conversion
date:   5 weeks ago
config: arc-randconfig-r131-20260302 (https://download.01.org/0day-ci/archive/20260302/202603021708.wwwXBbbO-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 14.3.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260302/202603021708.wwwXBbbO-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/202603021708.wwwXBbbO-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   fs/ext4/extents.c: note: in included file:
>> 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

    49	
    50	struct kunit_ctx {
    51		/*
    52		 * Ext4 inode which has only 1 unwrit extent
    53		 */
    54		struct ext4_inode_info *k_ei;
    55		/*
    56		 * Represents the underlying data area (used for zeroout testing)
    57		 */
    58		char *k_data;
  > 59	} k_ctx;
    60	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki