[akpm-mm:mm-new 291/296] include/linux/mm.h:944:31: sparse: sparse: incorrect type in argument 2 (different modifiers)

[akpm-mm:mm-new 291/296] include/linux/mm.h:944:31: sparse: sparse: incorrect type in argument 2 (different modifiers)

[kernel test robot]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
head:   02dafa01ec9a00c3758c1c6478d82fe601f5f1ba
commit: 85de428c7ca1b71457690b95e162662d0edb2792 [291/296] mm: set the VM_MAYBE_GUARD flag on guard region install
config: csky-randconfig-r121-20251110 (https://download.01.org/0day-ci/archive/20251110/202511101223.yntfHDDu-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251110/202511101223.yntfHDDu-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/202511101223.yntfHDDu-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   mm/madvise.c:562:9: sparse: sparse: context imbalance in 'madvise_cold_or_pageout_pte_range' - different lock contexts for basic block
   mm/madvise.c:781:9: sparse: sparse: context imbalance in 'madvise_free_pte_range' - different lock contexts for basic block
   mm/madvise.c: note: in included file (through include/linux/mman.h):
>> include/linux/mm.h:944:31: sparse: sparse: incorrect type in argument 2 (different modifiers) @@     expected unsigned long volatile *addr @@     got unsigned long [noderef] * @@
   include/linux/mm.h:944:31: sparse:     expected unsigned long volatile *addr
   include/linux/mm.h:944:31: sparse:     got unsigned long [noderef] *

vim +944 include/linux/mm.h

bf91f4ed2a530f Lorenzo Stoakes 2025-11-07  932  
bf91f4ed2a530f Lorenzo Stoakes 2025-11-07  933  /*
bf91f4ed2a530f Lorenzo Stoakes 2025-11-07  934   * Set VMA flag atomically. Requires only VMA/mmap read lock. Only specific
bf91f4ed2a530f Lorenzo Stoakes 2025-11-07  935   * valid flags are allowed to do this.
bf91f4ed2a530f Lorenzo Stoakes 2025-11-07  936   */
bf91f4ed2a530f Lorenzo Stoakes 2025-11-07  937  static inline void vma_flag_set_atomic(struct vm_area_struct *vma, int bit)
bf91f4ed2a530f Lorenzo Stoakes 2025-11-07  938  {
bf91f4ed2a530f Lorenzo Stoakes 2025-11-07  939  	/* mmap read lock/VMA read lock must be held. */
bf91f4ed2a530f Lorenzo Stoakes 2025-11-07  940  	if (!rwsem_is_locked(&vma->vm_mm->mmap_lock))
bf91f4ed2a530f Lorenzo Stoakes 2025-11-07  941  		vma_assert_locked(vma);
bf91f4ed2a530f Lorenzo Stoakes 2025-11-07  942  
bf91f4ed2a530f Lorenzo Stoakes 2025-11-07  943  	if (__vma_flag_atomic_valid(vma, bit))
bf91f4ed2a530f Lorenzo Stoakes 2025-11-07 @944  		set_bit(bit, &vma->__vm_flags);
bf91f4ed2a530f Lorenzo Stoakes 2025-11-07  945  }
bf91f4ed2a530f Lorenzo Stoakes 2025-11-07  946  

:::::: The code at line 944 was first introduced by commit
:::::: bf91f4ed2a530f2e55e7b202c1692a4c682888d6 mm: add atomic VMA flags and set VM_MAYBE_GUARD as such

:::::: TO: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
:::::: CC: Andrew Morton <akpm@linux-foundation.org>

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