On Fri, May 09, 2025 at 11:47:36PM +0800, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git untested.securityfs > head: b0b8e25f92ec20e266859de5f823b4e39b8e2f9d > commit: 08433f2507554980bc891d8b17c1968c81cb144b [6/8] ima_fs: don't bother with removal of files in directory we'll be removing > config: i386-buildonly-randconfig-006-20250509 (https://download.01.org/0day-ci/archive/20250509/202505092310.0UXOhVZP-lkp@xxxxxxxxx/config) > compiler: gcc-11 (Debian 11.3.0-12) 11.3.0 > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250509/202505092310.0UXOhVZP-lkp@xxxxxxxxx/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@xxxxxxxxx> > | Closes: https://lore.kernel.org/oe-kbuild-all/202505092310.0UXOhVZP-lkp@xxxxxxxxx/ > > All errors (new ones prefixed by >>): > > security/integrity/ima/ima_fs.c: In function 'ima_release_policy': > >> security/integrity/ima/ima_fs.c:524:27: error: 'ima_policy' undeclared (first use in this function); did you mean 'vma_policy'? > 524 | securityfs_remove(ima_policy); > | ^~~~~~~~~~ > | vma_policy > security/integrity/ima/ima_fs.c:524:27: note: each undeclared identifier is reported only once for each function it appears in Yeah, that line also needs to be removed - it's handled by securityfs_remove(ima_dir); a few lines later.
