linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* [linux-next:master 9549/9925] mm/kasan/common.c:280:6: sparse: sparse: symbol 'unpoison_slab_object' was not declared. Should it be static?
@ 2023-12-21 17:38 kernel test robot
  0 siblings, 0 replies; only message in thread
From: kernel test robot @ 2023-12-21 17:38 UTC (permalink / raw)
  To: Andrey Konovalov
  Cc: oe-kbuild-all, Linux Memory Management List, Andrew Morton

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   857647efa9be89a13cf8963c7e167fab062b28bb
commit: 7cd408d15052b2a3912781842ee7a11e6d9a4dcd [9549/9925] kasan: save alloc stack traces for mempool
config: x86_64-randconfig-123-20231221 (https://download.01.org/0day-ci/archive/20231222/202312220147.TAQKNUdL-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231222/202312220147.TAQKNUdL-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/202312220147.TAQKNUdL-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> mm/kasan/common.c:280:6: sparse: sparse: symbol 'unpoison_slab_object' was not declared. Should it be static?
>> mm/kasan/common.c:511:53: sparse: sparse: incorrect type in argument 3 (different base types) @@     expected restricted gfp_t [usertype] flags @@     got unsigned long [usertype] size @@
   mm/kasan/common.c:511:53: sparse:     expected restricted gfp_t [usertype] flags
   mm/kasan/common.c:511:53: sparse:     got unsigned long [usertype] size

vim +/unpoison_slab_object +280 mm/kasan/common.c

   279	
 > 280	void unpoison_slab_object(struct kmem_cache *cache, void *object, gfp_t flags,
   281				  bool init)
   282	{
   283		/*
   284		 * Unpoison the whole object. For kmalloc() allocations,
   285		 * poison_kmalloc_redzone() will do precise poisoning.
   286		 */
   287		kasan_unpoison(object, cache->object_size, init);
   288	
   289		/* Save alloc info (if possible) for non-kmalloc() allocations. */
   290		if (kasan_stack_collection_enabled() && !is_kmalloc_cache(cache))
   291			kasan_save_alloc_info(cache, object, flags);
   292	}
   293	

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


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-12-21 17:39 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-12-21 17:38 [linux-next:master 9549/9925] mm/kasan/common.c:280:6: sparse: sparse: symbol 'unpoison_slab_object' was not declared. Should it be static? kernel test robot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox