[kas:collapse/rfc-v1 66/76] mm/madvise.c:285:13: warning: 'mark_vma_lock_dropped' defined but not used

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/kas/linux.git collapse/rfc-v1
head:   efac4ce42bf9ea34a32d1563fe3370ee837a751f
commit: 0d2ea7c0b6b1a192e14fa351107df1ebec90a43b [66/76] mm/madvise: collapse under a per-VMA read lock
config: alpha-allmodconfig (https://download.01.org/0day-ci/archive/20260818/[email protected]/config)
compiler: alpha-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260818/[email protected]/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 <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/

All warnings (new ones prefixed by >>):

>> mm/madvise.c:285:13: warning: 'mark_vma_lock_dropped' defined but not used [-Wunused-function]
     285 | static void mark_vma_lock_dropped(struct madvise_behavior *madv_behavior)
         |             ^~~~~~~~~~~~~~~~~~~~~


vim +/mark_vma_lock_dropped +285 mm/madvise.c

   278	
   279	/*
   280	 * The VMA-lock counterpart, for a behaviour that releases the VMA it was handed
   281	 * and locks what it needs for itself.  The walk has nothing left to release,
   282	 * and unlike the mmap_lock case it has nothing to carry on with either: the VMA
   283	 * fast path applies to one VMA and returns.
   284	 */
 > 285	static void mark_vma_lock_dropped(struct madvise_behavior *madv_behavior)
   286	{
   287		VM_WARN_ON_ONCE(madv_behavior->lock_mode != MADVISE_VMA_READ_LOCK);
   288		madv_behavior->lock_dropped = true;
   289	}
   290	

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