Re: [RFC] vfs: security: Parse dev_name before calling security_sb_mount

[kernel test robot <lkp@intel.com>]

Hi Song,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:

[auto build test WARNING on brauner-vfs/vfs.all]
[also build test WARNING on pcmoore-selinux/next linus/master v6.16-rc5]
[cannot apply to viro-vfs/for-next next-20250709]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Song-Liu/vfs-security-Parse-dev_name-before-calling-security_sb_mount/20250709-070602
base:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link:    https://lore.kernel.org/r/20250708230504.3994335-1-song%40kernel.org
patch subject: [RFC] vfs: security: Parse dev_name before calling security_sb_mount
config: i386-buildonly-randconfig-003-20250709 (https://download.01.org/0day-ci/archive/20250709/202507092338.cQvAA2aV-lkp@intel.com/config)
compiler: clang version 20.1.7 (https://github.com/llvm/llvm-project 6146a88f60492b520a36f8f8f3231e15f3cc6082)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250709/202507092338.cQvAA2aV-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/202507092338.cQvAA2aV-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> Warning: security/tomoyo/mount.c:81 function parameter 'dev_path' not described in 'tomoyo_mount_acl'
>> Warning: security/tomoyo/mount.c:203 function parameter 'dev_path' not described in 'tomoyo_mount_permission'

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